[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-10-17 Thread Steve Beattie
Apparmor 2.9.0 has been released; closing. ** Changed in: apparmor Status: Fix Committed = Fix Released ** Changed in: linux (Ubuntu) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-10-15 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/utopic-proposed/apparmor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375516 Title: unix_socket_pathname.sh confined server stream/seqpacket missing

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Tyler Hicks
** Description changed: The AF_UNIX pathname stream and seqpacket tests are not failing when the server program is missing the getopt unix permission. Note that the dgram version of this test fails as expected. This suggests some type of difference in the mediation of getsockopt() between

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Tyler Hicks
After discussions in IRC, it was determined that this is expected behavior and that the test should be modified to remove the getopt permission from the list of server permissions. The unix_socket test program calls getsockopt() after calling bind(). Because AppArmor continues to use traditional

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Tyler Hicks
Patch tested and set to the list: https://lists.ubuntu.com/archives/apparmor/2014-September/006572.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375516 Title:

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Tyler Hicks
** Changed in: apparmor Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375516 Title: unix_socket_pathname.sh confined server stream/seqpacket

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Launchpad Bug Tracker
** Branch linked: lp:apparmor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375516 Title: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails Status

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-30 Thread Tyler Hicks
Committed to lp:apparmor as r2717. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1375516 Title: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

[Kernel-packages] [Bug 1375516] Re: unix_socket_pathname.sh confined server stream/seqpacket missing getopt test fails

2014-09-29 Thread Tyler Hicks
Since this issue affects stream/seqpacket but not dgram, it seems likely that it is a kernel issue and not a parser issue. But to be sure, I've verified that the perms that the parser outputs for setopt, getopt, and the combination of the two does look sane: $ for p in getopt setopt