netdev - Re: [PATCH bpf-next] selftests/bpf: don't hardcode iptables/nc path in test_tcpnotify

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: <126ed9cf-9e11-d830-e617-6aa74e9b4730@iogearbox.net>
Date:   Wed, 23 Jan 2019 12:57:33 +0100
From:   Daniel Borkmann <daniel@...earbox.net>
To:     Stanislav Fomichev <sdf@...gle.com>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, ast@...nel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: don't hardcode iptables/nc path
 in test_tcpnotify_user

On 01/17/2019 08:56 PM, Stanislav Fomichev wrote:
> system() is calling shell which should find the appropriate full path
> via $PATH. On some systems, full path to iptables and/or nc might be
> different that we one we have hardcoded.
> 
> Signed-off-by: Stanislav Fomichev <sdf@...gle.com>

Applied, thanks!