[apparmor] DBus rule syntax for subject and peer components

Jamie Strandboge jamie at canonical.com
Thu Jun 20 13:40:11 UTC 2013


On 06/17/2013 02:39 PM, Tyler Hicks wrote:
> 
> * Proposal 3.1 - Change subj= to subject=
> ...
> 
> dbus [<bus>] [subject=(<subject>)] [acquire],
> dbus [<bus>] [subject=(<subject>)] [peer=(<peer>)] [send | receive],

+1


> * Proposal 3.2 - Move the access to the front
> ...
> 
> dbus [acquire] [<bus>] [subject=(<subject>)] [acquire],
> dbus [send | receive] [<bus>] [subject=(<subject>)] [peer=(<peer>)],

+1

> * Proposal 3.3 - Drop the equal signs for grouping
> 
> ...
> dbus [<bus>] [subject(<subject>)] [acquire],
> dbus [<bus>] [subject(<subject>)] [peer(<peer>)] [send | receive],

-1


> * Proposal 3.4 - Replace the equal signs with a space for grouping
> 
> dbus [<bus>] [subject (<subject>)] [acquire],
> dbus [<bus>] [subject (<subject>)] [peer (<peer>)] [send | receive],

-1


> * Proposal 3.5 - Replace the equal signs with a space and use curly
>                  braces for grouping
> 
> dbus [<bus>] [subject {<subject>}] [acquire],
> dbus [<bus>] [subject {<subject>}] [peer {<peer>}] [send | receive],
> 

+0

I could live with this, but I prefer 'subject|peer=()' for DBus rules if
all we are considering is DBus syntax. If 'subject|peer {}' makes this
more consistent with other IPC, then +1.

> * Proposal 3.6 - Replace the equals signs with a space and use no
>                  characters for grouping
> 
> dbus [<bus>] [subject <subject>] [acquire],
> dbus [<bus>] [subject <subject>] [peer <peer>] [send | receive],

-1


-- 
Jamie Strandboge                 http://www.ubuntu.com/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/apparmor/attachments/20130620/2e9427ac/attachment.pgp>


More information about the AppArmor mailing list