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
| ||
|
Date: Thu, 14 Apr 2016 21:07:13 -0400 (EDT) From: David Miller <davem@...emloft.net> To: dhowells@...hat.com Cc: linux-afs@...ts.infradead.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify sendmsg() op From: David Howells <dhowells@...hat.com> Date: Tue, 12 Apr 2016 16:05:41 +0100 > Simplify the RxRPC user interface and remove the use of connect() to direct > client calls. It is redundant given that sendmsg() can be given the target > address and calls to multiple targets are permitted from a client socket > and also from a service socket. You can't just change completely the socket semantics for your protocol like this, every single userland application is going to break. Sorry, there is no way I am applying changes like this.
Powered by blists - more mailing lists