On 02/18/2016 08:22 AM, Tyler Hicks wrote:
> On 2016-02-17 22:29:23, John Johansen wrote:
>> On 02/17/2016 08:51 PM, Tyler Hicks wrote:
>>> 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
On 2016-02-18 18:19:39, Christian Boltz wrote:
> Hello,
>
> Am Mittwoch, 17. Februar 2016, 22:51:01 CET schrieb Tyler Hicks:
> > 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
Hello,
Am Mittwoch, 17. Februar 2016, 22:51:01 CET schrieb Tyler Hicks:
> 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
On 2016-02-17 22:29:23, John Johansen wrote:
> On 02/17/2016 08:51 PM, Tyler Hicks wrote:
> > 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
On 02/17/2016 08:51 PM, Tyler Hicks wrote:
> 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
>
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
