On 07/09/2013 07:56 PM, Seth Arnold wrote:
> On Sun, Jul 07, 2013 at 08:46:31PM -0500, Jamie Strandboge wrote:
>> Attached is a patch to address Seth's comments, and a few more fixes. After
>> submitting the last patch, we discussed the JSON structure[1] a bit more, and
>> realized that it needed a
On Sun, Jul 07, 2013 at 08:46:31PM -0500, Jamie Strandboge wrote:
> Attached is a patch to address Seth's comments, and a few more fixes. After
> submitting the last patch, we discussed the JSON structure[1] a bit more, and
> realized that it needed a refinement. In particular, rather than having
>
On Sat, Jul 06, 2013 at 12:37:20PM -0500, Jamie Strandboge wrote:
> > There's a race condition here; well, maybe not -race-, but
> > self.template is updated before the sanity checks are performed. If
> > either of those exceptions gets ignored in callers, the template is
> > set to unsafe values.
On Mon, Jul 08, 2013 at 05:36:45PM -0700, Seth Arnold wrote:
> So, how about the following, to fix both problems? (I picked @options as
> the solution -- to match the path among items in the list.)
>
> Proposed for trunk and 2.8:
>
> Acked-by: Seth Arnold
Acked-by: Steve Beattie for both
Than
On 07/09/2013 08:55 AM, John Johansen wrote:
> On 07/09/2013 05:15 AM, John Johansen wrote:
>>
>> As long as a type does not imply binding an address with creation it
>> will get an implicit rule that allows creation and default labeling
>> of the type without a rule, and a task will be allowed to
Hello,
On Wed, Jul 10, 2013 at 12:09 AM, Christian Boltz wrote:
> I noticed you removed repr() in r16 - does this fix the issue?
> (a short test tells me the answer is probably "no")
>
Actually it did, but then I moved to the error() thing in r16.
Also, its standard to use repr(), so I'll rever
Hello,
Am Dienstag, 9. Juli 2013 schrieb Kshitij Gupta:
> >> I somehow doubt this is intentional - the test should catch this
> >> exception ;-)
>
> As it turns this issue has got something to do with the Python3's new
> feature called Exception Chaining.
> Its another of those Python2-3 problem.
Hello,
Am Dienstag, 9. Juli 2013 schrieb Kshitij Gupta:
> === added file 'apparmor/aa.py'
> --- apparmor/aa.py1970-01-01 00:00:00 +
> +++ apparmor/aa.py2013-07-06 13:27:06 +
> +# Setup logging incase of debugging is enabled
> +if os.getenv('LOGPROF_DEBUG', False):
> +import lo
Hello,
same as last time - see attached file ;-)
Regards,
Christian Boltz
--
who needs facts if polemics are that much easier to get into.
[Sven Burmeister in opensuse-factory]
=== modified file 'Testing/severity_test.py'
--- Testing/severity_test.py 2013-07-06 13:27:06 +
+++ Testing/sever
On 07/09/2013 05:15 AM, John Johansen wrote:
>
> As long as a type does not imply binding an address with creation it
> will get an implicit rule that allows creation and default labeling
> of the type without a rule, and a task will be allowed to communicate
> with its own label by default.
>
>
So to expand on this for general ipc syntax. After discussing this more
in a mumble based chat we reached have settled on a general direction.
That has a format similar to that outlined by Tyler with the dbus
syntax.
New rules will start with a type keyword (eg. dbus) followed by the
permission se
On 07/09/2013 12:05 AM, Tyler Hicks wrote:
> After gathering everyone's opinions[1] on the DBus syntax, John's wider
> discussion[2] of IPC syntax, and various other conversations, I think
> we've come to a conclusion on what the DBus syntax should look like.
> I'll begin adjusting the existing par
Hello,
Here's the progress report from Week 3 of my project:
http://kshitijblogs.blogspot.com/2013/07/week-3.html
Regards,
Kshitij Gupta
--
AppArmor mailing list
AppArmor@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/apparmor
13 matches
Mail list logo
