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: <20190218.172544.1436352995315454863.davem@davemloft.net> Date: Mon, 18 Feb 2019 17:25:44 -0800 (PST) From: David Miller <davem@...emloft.net> To: s-nazarov@...dex.ru Cc: paul@...l-moore.com, netdev@...r.kernel.org, linux-security-module@...r.kernel.org, kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org Subject: Re: [PATCH] NETWORKING: avoid use IPCB in cipso_v4_error From: Nazarov Sergey <s-nazarov@...dex.ru> Date: Mon, 18 Feb 2019 16:39:11 +0300 > I think, it would not be a good solution, if I will analyze all > subsystems using icmp_send, because I do not have enough knowledge > for this. I propose to add a new function, for example, > ismp_send_safe, something like that: Please don't do this. Solve the problem properly by auditing each case, there aren't a lot and it is not too difficult to see the upcall sites.
Powered by blists - more mailing lists