On Thu, Dec 19, 2019 at 11:42 AM Dmitry Vyukov <dvyukov@xxxxxxxxxx> 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.
