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
| ||
|
Message-Id: <20101030.121238.189687981.davem@davemloft.net> Date: Sat, 30 Oct 2010 12:12:38 -0700 (PDT) From: David Miller <davem@...emloft.net> To: segooon@...il.com Cc: kernel-janitors@...r.kernel.org, ebiederm@...ssion.com, eric.dumazet@...il.com, tj@...nel.org, serge@...lyn.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] net: core: scm: fix information leak to userland Your patches are almost entirely baseless. You haven't even made an effort to show a real case, in detail, where your patches actually fix a bug. The CMSG case shows that you didn't even bother to look at the assembly of even one architecture to see if padding bytes even existed in the structure, and that furthermore even if they existed that they would leak out ever. I don't even buy the "preventative nature" argument for the address[128] thing. If a protocol is leaking kernel memory in that case, it also isn't filling in the address value properly, which is a bug times two. I absolutely am not applying these patches, sorry. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists