apparmor/common
Tyler Hicks 9b2aa90b06 parser: Allow AF_UNSPEC family in network rules
https://launchpad.net/bugs/1546455

Don't filter out AF_UNSPEC from the list of valid protocol families so
that the parser will accept rules such as 'network unspec,'.

There are certain syscalls, such as socket(2), where the LSM hooks are
called before the protocol family is validated. In these cases, AppArmor
was emitting denials even though socket(2) will eventually fail. There
may be cases where AF_UNSPEC sockets are accepted and we need to make
sure that we're mediating those appropriately.

Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Suggested-by: Steve Beattie <steve@nxnw.org>
Acked-by: John Johansen <john.johansen@canonical.com>
[cboltz: Add 'unspec' to the network domain keywords of the utils]
2016-02-18 12:35:35 -06:00
..
apparmor.css Subject: Move make targets from docs/ to common/Make.rules 2007-04-03 18:51:56 +00:00
Make-po.rules binutils: Add aa-enabled program to check AppArmor status 2015-12-16 18:35:09 -06:00
Make.rules parser: Allow AF_UNSPEC family in network rules 2016-02-18 12:35:35 -06:00
Version Update version in preparation for a 2.11 release 2015-11-18 01:34:50 -08:00