linux-kernel - Re: [PATCH net-next v2] net: WireGuard secure network tunnel

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHmME9pe1XNfT5LN0---WQgQYEHVaFRC9fkqTBsTYcU6GbGnFA@mail.gmail.com>
Date:   Thu, 19 Dec 2019 11:50:21 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     netdev <netdev@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        Greg KH <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" 
        <linux-crypto@...r.kernel.org>
Subject: Re: [PATCH net-next v2] net: WireGuard secure network tunnel

On Thu, Dec 19, 2019 at 11:42 AM Dmitry Vyukov <dvyukov@...gle.com> wrote:
> Well, unfortunately it does not test wireguard at the moment. I've
> enabled the config as I saw it appeared in linux-next:
> https://github.com/google/syzkaller/commit/240ba66ba8a0a99f27e1aac01f376331051a65c2
> but that's it for now.

I do see that in the linux-next and net-next instances you have
running, it's at least hitting interface creation and netlink.

> There are 3000 subsystems, are you ready to describe precise interface
> for all of them with all the necessary setup and prerequisites? Nobody
> can do it for all subsystems. Developer of a particular subsystem is
> the best candidate for also describing what it takes to test it ;)

Sure, I'd be happy to help get things rolling on WireGuard. What do
you need from me? A small shell script to set up a few interfaces that
are peered with each other? Sample packets to begin mutations from?
Since most of WireGuard's surface is behind constant-time/branchless
crypto, I doubt you'll fuzz your way to having valid key agreement,
which makes me think some sort of setup is necessary.