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: <CE5C7791-1811-48AC-807B-D49ADD9068AA@oracle.com> Date: Mon, 3 Jan 2022 16:16:47 +0000 From: Haakon Bugge <haakon.bugge@...cle.com> To: "Liu, Congyu" <liu3101@...due.edu> CC: "rds-devel@....oracle.com" <rds-devel@....oracle.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, Santosh Shilimkar <santosh.shilimkar@...cle.com>, Mark Haywood <mark.haywood@...cle.com> Subject: Re: RDS: Can RDS sockets from different network namespace bind to the same address? +mark > On 16 Dec 2021, at 02:32, Liu, Congyu <liu3101@...due.edu> wrote: > > Hi, > > (Resend this email in plain text in case the previous one was spammed. Sorry for the trouble caused.) > > I am writing to ask about if two RDS sockets from different network namespaces can bind to the same address. > > I am doing research on container security. Recently our tool produced a simple test case with confusing test result: there are two network namespaces A and B. Both A and B has a tun device, and these two tun devices have the same IPv4 address. In namespace A a RDS socket is created and binds it to namespace A's tun device. It works. But then in namespace B the other RDS socket is created and binds it to namespace B's tun device, it fails with error code EADDRINUSE. Is this considered as expected behavior? > > > Thanks, > Congyu
Powered by blists - more mailing lists