5 ms·
Sadly looks like WireGuard missed the cut again
by swrobel 7y ago
Sadly looks like WireGuard missed the cut again
- NullPrefix 7y agoWouldn't expect something like that to be merged as late as as rc8.
- geophertz 7y agoProbably won't be in before 5.5: https://www.phoronix.com/scan.php?page=news_item&px=WireGuard-0.0.20190913 https://www.phoronix.com/scan.php?page=news_item&px=WireGuar...
- simcop2387 7y agoThere's still progress being made, but WireGuard does do a lot of things to/for the in-kernel cryptography stuff. That's been the major holdup for getting it in. There's some that don't like that a new api is being made at all but I believe most are fine with that as long it shares as much internally as possible with the existing code so that there's not two copies of everything. A lot of that has been done last I heard but it wasn't quite ready yet for mainlining in that fashion. I suspect we'll see another RFC for it in the 5.4 merge window and maybe finally some traction at getting it into staging or all the way in. EDIT: see sibling comment about wireguard and 5.4, apparently not slated for it this time but maybe 5.5.
- tssva 7y agoLast patch set I remember seeing was v9 submitted to the mailing list in March. There was some feedback regarding the new zinc crypto interface and replacement crypto implementations. Jason indicated he would address them for the next patch submission which I don't believe has been made yet.