netdev - Re: [PATCH v3 net-next 0/4] l2tp: set l2specific_len based on l2specific

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEwTi7Snb0zE8R7dCCMXvK5LFkH4HdjRRm2S6Seiu+OHA+qmTg@mail.gmail.com>
Date:   Wed, 17 Jan 2018 14:56:41 +0000
From:   James Chapman <jchapman@...alix.com>
To:     Lorenzo Bianconi <lorenzo.bianconi@...hat.com>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Guillaume Nault <g.nault@...halink.fr>, netdev@...r.kernel.org
Subject: Re: [PATCH v3 net-next 0/4] l2tp: set l2specific_len based on l2specific_type

On 17 January 2018 at 10:23, Guillaume Nault <g.nault@...halink.fr> wrote:
> On Tue, Jan 16, 2018 at 11:01:53PM +0100, Lorenzo Bianconi wrote:
>> Do not rely on l2specific_len value provided by userspace but set sublayer
>> length according to l2specific_type.
>> Mark L2TP_ATTR_L2SPEC_LEN attribute as not used
>>
> Nice. Thanks for doing this work Lorenzo.

Acked-by: James Chapman <jchapman@...alix.com>