netdev - Re: [PATCH net-next] fcnal-test: Fix vrf argument in local tcp tests

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20200106.134718.1421984985726144048.davem@redhat.com>
Date:   Mon, 06 Jan 2020 13:47:18 -0800 (PST)
From:   David Miller <davem@...hat.com>
To:     dsahern@...nel.org
Cc:     jakub.kicinski@...ronome.com, netdev@...r.kernel.org,
        dsahern@...il.com
Subject: Re: [PATCH net-next] fcnal-test: Fix vrf argument in local tcp
 tests

From: David Ahern <dsahern@...nel.org>
Date: Sun,  5 Jan 2020 20:02:05 -0800

> From: David Ahern <dsahern@...il.com>
> 
> The recent MD5 tests added duplicate configuration in the default VRF.
> This change exposed a bug in existing tests designed to verify no
> connection when client and server are not in the same domain. The
> server should be running bound to the vrf device with the client run
> in the default VRF (the -2 option is meant for validating connection
> data). Fix the option for both tests.
> 
> While technically this is a bug in previous releases, the tests are
> properly failing since the default VRF does not have any routing
> configuration so there really is no need to backport to prior releases.
> 
> Signed-off-by: David Ahern <dsahern@...il.com>

Applied.