netdev - Re: [PATCH net-next 0/1] wireguard column reformatting for end of cycle

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: <20200601.144008.2114976182852633034.davem@davemloft.net>
Date:   Mon, 01 Jun 2020 14:40:08 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     mkubecek@...e.cz
Cc:     Jason@...c4.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/1] wireguard column reformatting for end of
 cycle

From: Michal Kubecek <mkubecek@...e.cz>
Date: Mon, 1 Jun 2020 23:13:07 +0200

> On Mon, Jun 01, 2020 at 01:33:46PM -0600, Jason A. Donenfeld wrote:
>> This possibility had occurred to me too, which is why I mentioned the
>> project being sufficiently young that this can work out. It's not
>> actually in any LTS yet, which means at the worst, this will apply
>> temporarily for 5.6,
> 
> It's not only about stable. The code has been backported e.g. into SLE15
> SP2 and openSUSE Leap 15.2 kernels which which are deep in RC phase so
> that we would face the choice between backporting this huge patch in
> a maintenance update and keeping to stumble over it in most of future
> backports (for years). Neither is very appealing (to put it mildly).
> I have no idea how many other distributions would be affected or for how
> long but I doubt we are the only ones.

And google and Facebook and twitter and Amazon and whatever else major
infrastructure provider decides to pull Wireguard into their tree.

Jason, I bet you're pretty happy about the uptake of Wireguard but
that popularity and distribution has consequences.  Small things have
huge ramifications for developers all over the place who now have to
keep up with your work and do backports of your fixes.