netdev - Re: [PATCH net-next] kcm: do not attach sockets if sk_user

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <1516122659.3606.9.camel@gmail.com>
Date:   Tue, 16 Jan 2018 09:10:59 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Guillaume Nault <g.nault@...halink.fr>,
        Tom Herbert <tom@...bertland.com>
Cc:     netdev@...r.kernel.org, James Chapman <jchapman@...alix.com>
Subject: Re: [PATCH net-next] kcm: do not attach sockets if sk_user_data is
 already used

On Tue, 2018-01-16 at 11:44 +0100, Guillaume Nault wrote:
> 
> Tom, if I understand KCM correctly, it only makes sense to attach it to
> SOCK_STREAM sockets. Shouldn't that be enforced? Maybe we should
> restrict it even further, so that only known KCM-safe sockets could be
> attached (that is, reject anything that isn't AF_INET* | SOCK_STREAM).


I believe I asked the same question months ago. I had no answer.

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/comm
it/?id=351050ecd6523374b370341cc29fe61e2201556b

Not sure if anyone uses KCM, other than fuzzers ?