Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Tyler Hicks
On 2013-06-12 20:50:05, Jamie Strandboge wrote: > On 06/12/2013 08:34 PM, Jamie Strandboge wrote: > > > I strongly prefer Proposal #3 over #1, #2 and #4. My personal preference > > is for 'peer=()' and 'subject=()' instead of 'peer {}' and 'subject {}', > > but I could live with '{}'. I think I so

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Jamie Strandboge
On 06/12/2013 08:34 PM, Jamie Strandboge wrote: > I strongly prefer Proposal #3 over #1, #2 and #4. My personal preference > is for 'peer=()' and 'subject=()' instead of 'peer {}' and 'subject {}', > but I could live with '{}'. I think I somewhat prefer the access at the > front (right after dbus)

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Jamie Strandboge
On 06/12/2013 06:36 PM, Seth Arnold wrote: > On Wed, Jun 12, 2013 at 03:42:34PM -0500, Jamie Strandboge wrote: >>> So, here's a first shot at Proposal #4: >>> [...] >>> /usr/bin/gnome-screensaver { >>> # Ignore file and accessibility bus access for this excercise >>> file, >>> dbus bus=access

Re: [apparmor] [patch] fix libapparmor ruby bindings for ruby 2.0

2013-06-12 Thread Seth Arnold
On Thu, Jun 13, 2013 at 12:25:23AM +0200, Christian Boltz wrote: > The patch fixes this problem, but as I already said, I'm not sure if > it's the best way to fix it. I'm not even sure if it's a bug in our > extconf.rb, in swig or if mkmf from Ruby 2.0 is buggy ;-) Your signature is again releva

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread John Johansen
On 06/12/2013 01:42 PM, Jamie Strandboge wrote: > On 06/12/2013 01:40 PM, Steve Beattie wrote: >> On Tue, Jun 11, 2013 at 02:41:03PM -0700, Tyler Hicks wrote: <> >>> If we distill that down a little bit, it means that the only subj >>> conditionals that make sense with send are name and label and

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread John Johansen
On 06/12/2013 01:28 PM, Jamie Strandboge wrote: > On 06/12/2013 02:13 PM, Tyler Hicks wrote: >> On 2013-06-11 23:30:58, John Johansen wrote: >>> On 06/11/2013 03:04 PM, Jamie Strandboge wrote: On 06/11/2013 04:41 PM, Tyler Hicks wrote: ... > As a side note, one thing that I'

Re: [apparmor] [patch] fix libapparmor ruby bindings for ruby 2.0

2013-06-12 Thread John Johansen
On 06/12/2013 03:25 PM, Christian Boltz wrote: > Hello, > > Am Mittwoch, 12. Juni 2013 schrieb John Johansen: >> On 06/05/2013 01:23 PM, Christian Boltz wrote: >>> you might have noticed the discussion about the libapparmor ruby >>> bindings build failures on openSUSE Factory, which is the first >

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Seth Arnold
On Wed, Jun 12, 2013 at 03:42:34PM -0500, Jamie Strandboge wrote: > > So, here's a first shot at Proposal #4: > > [...] > > /usr/bin/gnome-screensaver { > > # Ignore file and accessibility bus access for this excercise > > file, > > dbus bus=accessibility, > > > > # sarnold> I think we cou

Re: [apparmor] [patch] fix libapparmor ruby bindings for ruby 2.0

2013-06-12 Thread Christian Boltz
Hello, Am Mittwoch, 12. Juni 2013 schrieb John Johansen: > On 06/05/2013 01:23 PM, Christian Boltz wrote: > > you might have noticed the discussion about the libapparmor ruby > > bindings build failures on openSUSE Factory, which is the first > > version with ruby 2.0. > > > > The problem was tha

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Tyler Hicks
On 2013-06-12 11:40:18, Steve Beattie wrote: > On Tue, Jun 11, 2013 at 02:41:03PM -0700, Tyler Hicks wrote: > > > * Proposal 3 - Grouping of subject and peer address components > > > > > > Based on Steve's suggestion[4] and refined by Jamie[5]. It groups the > > > connection attributes together ba

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Jamie Strandboge
On 06/11/2013 08:46 PM, Seth Arnold wrote: > On Mon, Jun 10, 2013 at 06:44:13PM -0700, Tyler Hicks wrote: >> To start us off, here's the profile using the current DBus syntax. It is >> complex, but it uses all of the DBus accesses (send, receive, and >> acquire) and it is representative of what a r

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Jamie Strandboge
On 06/12/2013 01:40 PM, Steve Beattie wrote: > On Tue, Jun 11, 2013 at 02:41:03PM -0700, Tyler Hicks wrote: >>> * Proposal 3 - Grouping of subject and peer address components >>> >>> Based on Steve's suggestion[4] and refined by Jamie[5]. It groups the >>> connection attributes together based on wh

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Jamie Strandboge
On 06/12/2013 02:13 PM, Tyler Hicks wrote: > On 2013-06-11 23:30:58, John Johansen wrote: >> On 06/11/2013 03:04 PM, Jamie Strandboge wrote: >>> On 06/11/2013 04:41 PM, Tyler Hicks wrote: >>> >>> ... >>> As a side note, one thing that I'm not real happy about is the asymmetry of send and

[apparmor] [Merge] lp:~kensington/apparmor/apparmor into lp:apparmor

2013-06-12 Thread Michael
Michael has proposed merging lp:~kensington/apparmor/apparmor into lp:apparmor. Requested reviews: AppArmor Developers (apparmor-dev) For more details, see: https://code.launchpad.net/~kensington/apparmor/apparmor/+merge/169010 The hu linguas is missing a couple of key shortcuts, which can cau

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Tyler Hicks
On 2013-06-11 23:30:58, John Johansen wrote: > On 06/11/2013 03:04 PM, Jamie Strandboge wrote: > > On 06/11/2013 04:41 PM, Tyler Hicks wrote: > > > > ... > > > >> As a side note, one thing that I'm not real happy about is the asymmetry > >> of send and receive rules. > >> > >> When writing a send

Re: [apparmor] DBus rule syntax for subject and peer components

2013-06-12 Thread Steve Beattie
On Tue, Jun 11, 2013 at 02:41:03PM -0700, Tyler Hicks wrote: > > * Proposal 3 - Grouping of subject and peer address components > > > > Based on Steve's suggestion[4] and refined by Jamie[5]. It groups the > > connection attributes together based on whether it is the subject's > > connection > >

Re: [apparmor] [opensuse-project] Google Summer of Code'13 accepted student

2013-06-12 Thread Seth Arnold
On Wed, Jun 12, 2013 at 10:55:50AM -0700, John Johansen wrote: > > Till then, can someone help me out with the use case for the write > > function of the profile tools? I'm not sure if I'm thinking in the > > appropriate way. How are users expected to modify the config files? > > I can understand r

Re: [apparmor] [opensuse-project] Google Summer of Code'13 accepted student

2013-06-12 Thread John Johansen
On 06/12/2013 09:25 AM, Kshitij Gupta wrote: > Hello, > > Yesterday, in the meeting we had started a discussion about configprofiler > and the comments, which was abruptly interrupted by my net connection. I > apologise for the same, its very rare for my net connection to behave that > way. >

Re: [apparmor] [opensuse-project] Google Summer of Code'13 accepted student

2013-06-12 Thread Kshitij Gupta
Hello, Yesterday, in the meeting we had started a discussion about configprofiler and the comments, which was abruptly interrupted by my net connection. I apologise for the same, its very rare for my net connection to behave that way. I missed out on parts on part of the conversations, I hope to

Re: [apparmor] [patch] fix libapparmor ruby bindings for ruby 2.0

2013-06-12 Thread John Johansen
On 06/11/2013 04:27 PM, Steve Beattie wrote: > On Wed, Jun 05, 2013 at 10:23:41PM +0200, Christian Boltz wrote: >> you might have noticed the discussion about the libapparmor ruby >> bindings build failures on openSUSE Factory, which is the first version >> with ruby 2.0. >> >> The problem was th

Re: [apparmor] [patch] fix libapparmor ruby bindings for ruby 2.0

2013-06-12 Thread John Johansen
On 06/05/2013 01:23 PM, Christian Boltz wrote: > Hello, > > you might have noticed the discussion about the libapparmor ruby > bindings build failures on openSUSE Factory, which is the first version > with ruby 2.0. > > The problem was that DESTDIR was added to too many variables, which > fina