| apw | zx2c4, you would prefer to have the latest wireguard dkms in our older series i assume yes; given your compatibility model | 12:09 |
|---|---|---|
| zx2c4 | apw: always always always have the latest | 12:18 |
| zx2c4 | Unless you provide a really compelling reason, i wont give any support to older versions | 12:18 |
| zx2c4 | So while we're before freeze, just always bunp | 12:19 |
| zx2c4 | Bump | 12:19 |
| zx2c4 | apw: DalekSec https://lists.zx2c4.com/pipermail/wireguard/2020-February/005013.html | 13:41 |
| zx2c4 | (has the fixes i pushed out for 5.6-rc2) | 13:41 |
| apw | zx2c4, the description of that implies we should not be expecting to see it packaged as yet | 14:27 |
| zx2c4 | apw: i have no idea what you could possibly be referring to or what you even mean | 14:30 |
| zx2c4 | but just for the avoidance of doubt, go by this statement: everytime there's a new signed tarball available on https://git.zx2c4.com/wireguard-linux-compat/refs/ the wireguard-dkms package should be bumped everyplace that you can possibly bump it | 14:31 |
| apw | Please note that until Linux 5.6 is released, this snapshot is a | 14:32 |
| apw | snapshot rather than a secure final release. | 14:32 |
| apw | that text says "don't put me in a distro" | 14:32 |
| zx2c4 | apw: that is a toned down version of the text that has been in every set of release notes for the last 4 years | 14:33 |
| zx2c4 | we're at v0 until 5.6 is cut. then it's v1. until then, we're releasing new snapshots with all the fixes from the various rcs from 5.6 | 14:34 |
| zx2c4 | i have no plans to skimp on maintenance of the linux-compat stuff -- important to keep parity for as long as possible | 14:34 |
| apw | zx2c4, huh, the debian package we are using is 1.x | 14:34 |
| apw | oh that is the wireguard tools i presume | 14:35 |
| zx2c4 | Yea the tools got v1'd a while ago | 14:35 |
| zx2c4 | https://github.com/google/syzkaller/commit/c5ed587f4af5e639f7373d8ebf10ac049cb9c71b | 14:36 |
| zx2c4 | Been doing some nice fuzzing | 14:36 |
| apw | the split being in one series and not anohter is confusing me | 14:36 |
| zx2c4 | Different packages, different versions | 14:37 |
| apw | yep, but what i was used to was one version to rule them all | 14:38 |
| zx2c4 | Ah yea, we got rid of the monolithic repo a while ago. I sent 4 emails about that and followed up with you a few times. But you never responded until i finally tracked you down here, remember? Makes sense its confusing still because you never "lived through" the transition like the rest of the packagers | 14:39 |
| zx2c4 | But indeed thats the situation - compat repo will be v0 until 5.6. Tools repo is v1 | 14:40 |
| zx2c4 | Right now there's a new compat release every rc | 14:40 |
| zx2c4 | Thatll probably slow down to every mainline release after 5.6 | 14:40 |
| zx2c4 | Unless security etc | 14:40 |
| zx2c4 | Also after focal freezes, if there is security stuff, ill be sure to let you know in here | 14:42 |
| apw | zx2c4, yeah i am aware, i just managed to ignore the knowledge when looking at rmadision output | 14:49 |
| apw | zx2c4, if it is serious you can come to me privatly too | 14:49 |
| zx2c4 | idunno | 15:51 |
| zx2c4 | ive full disclosured so many security vulns | 15:51 |
| zx2c4 | seems like it'd be a weird twist of irony of i started getting secretive about my own stuff :-P | 15:51 |
| apw | zx2c4, heh, as you will | 16:00 |
| zx2c4 | s/"disclosured"/disclosed | 16:01 |
| zx2c4 | https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d114b9fe78c8d6fc6e70808c2092aa307c36dc8e like putting exploit code in commit messages... | 16:02 |
| zx2c4 | the most coordinated of coordinated disclosure :D | 16:03 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!