On 5/19/20 12:17 AM, Andrey Ignatov wrote:
Daniel Borkmann [Mon, 2020-05-18 08:35 -0700]:
Extend the existing connect_force_port test to assert get{peer,sock}name
programs
as well. The workflow for e.g. IPv4 is as follows: i) server binds to concrete
port, ii) client calls getsockname() on ser
Daniel Borkmann [Mon, 2020-05-18 08:35 -0700]:
> Extend the existing connect_force_port test to assert get{peer,sock}name
> programs
> as well. The workflow for e.g. IPv4 is as follows: i) server binds to concrete
> port, ii) client calls getsockname() on server fd which exposes 1.2.3.4:6
>
Extend the existing connect_force_port test to assert get{peer,sock}name
programs
as well. The workflow for e.g. IPv4 is as follows: i) server binds to concrete
port, ii) client calls getsockname() on server fd which exposes 1.2.3.4:6 to
client, iii) client connects to service address 1.2.3.4:
