00:01:07dm4v quits [Read error: Connection reset by peer]
00:03:39dm4v joins
00:03:41dm4v quits [Changing host]
00:03:41dm4v (dm4v) joins
00:04:35wolfin quits [Quit: ZNC - https://znc.in]
00:23:17Arcorann (Arcorann) joins
00:33:34wickedplayer494 quits [Ping timeout: 252 seconds]
00:36:40Meli quits [Ping timeout: 265 seconds]
00:38:44wickedplayer494 joins
00:41:33Meli (Meli) joins
00:43:22sonick (sonick) joins
01:03:43dm4v_ joins
01:04:22dm4v quits [Ping timeout: 252 seconds]
01:04:22dm4v_ is now known as dm4v
01:04:22dm4v quits [Changing host]
01:04:22dm4v (dm4v) joins
02:49:34<pabs>https://kylechayka.substack.com/p/essay-the-digital-death-of-collecting
04:04:13mutantmonkey quits [Remote host closed the connection]
04:04:33mutantmonkey (mutantmonkey) joins
04:35:31wolfin (wolfin) joins
05:18:54Wingy quits [Client Quit]
05:19:37Wingy (Wingy) joins
08:31:46sonick quits [Client Quit]
10:07:46Sluggs quits [Ping timeout: 252 seconds]
10:11:02Sluggs joins
10:49:25lunik1 quits [Quit: :x]
10:50:05lunik1 joins
10:51:46sonick (sonick) joins
12:58:05knecht420 quits [Quit: The Lounge - https://thelounge.chat]
12:58:32knecht420 (knecht420) joins
13:00:22knecht420 quits [Client Quit]
13:00:51knecht420 (knecht420) joins
13:58:22Minkafighter quits [Quit: The Lounge - https://thelounge.chat]
13:58:42Minkafighter joins
14:04:38<IDK>Socialbot: https://usercontent.irccloud-cdn.com/file/Rzp6eKl7/image.png
15:14:07Arcorann quits [Ping timeout: 252 seconds]
15:28:54qwertyasdfuiopghjkl quits [Remote host closed the connection]
15:37:41Matthww0 joins
15:38:34Matthww quits [Ping timeout: 265 seconds]
15:38:34Matthww0 is now known as Matthww
15:50:09atphoenix (atphoenix) joins
16:23:32lukash7 joins
17:09:04<atphoenix>not sure if this affected anyone else, but it appears that HexChat 2.14.x was no longer able to connect to hackint as of sometime on 9/30. The just-released (10/1) version 2.16 is able to connect.
17:09:51<atphoenix>but of course if anyone is still on the older version, they probably aren't here to see that message...
17:10:45<hexa->related to root certificate verification
17:10:50<hexa->letsencrypts old root expired
17:10:56<hexa->the intermediate is cross-signed
17:11:04<hexa->some implementations fail early
17:12:20<atphoenix>the Hexchat changelogs didn't explicitly mention the LetsEncrypt certs, but did mention an OpenSSL update, so it's probably buried in there
17:15:53<hexa->yup, that's related
17:20:56<Barto>libressl had to make a bugfix to check that cross signature
17:23:15<@JAA>1.5 years ago, yeah.
17:23:38<hexa->fwiw I had the issue on Android 11 with WPA2-eAP
17:23:51<hexa->had to specify the explicit root instead of "Use the system store"
17:24:15<@JAA>Isn't it amazing that basically every TLS implementation out there is broken?
17:24:20<@JAA>Or was, anyway.
17:24:27<@JAA>You'd think that shit gets tested thoroughly.
17:24:40<kiska>What do you mean lowest bidder :p
17:24:59<kiska>Or some variation of that
17:25:18<Barto>well... i wonder how they testsuite is looking like
17:25:57<hexa->better now
17:33:40<@JAA>To be fair, the relevant section of the X.509 RFC is horrible: https://datatracker.ietf.org/doc/html/rfc5280#section-6
18:33:29<h3ndr1k><JAA> Or was, anyway.
18:33:29<h3ndr1k>Is broken, we just don't know of all the current problems ^^
18:34:49<@JAA>Well yeah, I just meant this particular issue, which I think is covered by the RFC already.
18:35:07<@JAA>And yet OpenSSL, LibreSSL, and GnuTLS all failed to take it into account until last year or so.
18:35:52<@JAA>Not sure about the browser SSL libraries, but I suspect those were also patched at some point, just quietly because nobody uses those directly.
18:56:47<grawity>NSS already deals with it fine (as far back as Firefox 24), as does Windows schannel (the Federal PKI cross-signing graph it has to deal with makes the LE situation look downright trivial)
18:57:30<grawity>but also, there seems to be a surprising amount of Windows users who've disabled all the "automatic ca updates" and never had the new root in the first place
19:05:03sec^nd quits [Ping timeout: 258 seconds]
19:10:23sec^nd (second) joins
19:56:01<atphoenix>until the update released yesterday, HexChat's previous update was all the way back in late Dec 2019. And per https://hexchat.github.io/news/2.16.0.html it is undermaintained/help wanted, so there wasn't really a way for HexChat users to stay much more current unless perhaps they compiled their own builds
19:58:09<atphoenix>well, I guess perhaps Windows users could have swapped in newer OpenSSL libcrypto DLLs into C:\Program Files\HexChat , if they had noticed the old DLLs
19:58:47<atphoenix>and libssl DLLs
19:58:55<@JAA>I definitely don't miss DLL hell.
19:59:22<hexa->fun fact: we were waiting for a release to be included in their network list
19:59:28<hexa->i wonder if we are now
20:00:04<hexa->https://github.com/hexchat/hexchat/pull/2272
20:00:25<hexa->apparently we are
20:00:36<atphoenix>if by DLL hell, you are referring to conflicting incompatible DLL versions, this isn't exactly a DLL hell case
20:01:38<atphoenix>if by DLL hell, you're referring to how-to-maintain-multiple private copies of DLLs at current versions, this could be a case
20:03:14<@JAA>Yeah, I mean the latter, DLLs spread all over the place and impossible to properly keep track of.
20:03:23<atphoenix>so https://en.wikipedia.org/wiki/DLL_Hell#Incompatible_versions vs https://en.wikipedia.org/wiki/DLL_Hell#Lack_of_serviceability
20:03:25<@JAA>But the former is just as horrible.
20:09:28Atom__ quits [Ping timeout: 252 seconds]
20:10:27<Ryz>Ah yes, when I have to find something something for me to play a Multimedia Fusion game months ago and had to find a .dll, had to go https://www.dll-files.com/
20:10:43<Ryz>...Reminds me, I wanna also archive that website via AB but the download stuff is gonna be an issue
20:12:38qw3rty joins
20:27:33HP_Archivist (HP_Archivist) joins
21:02:51Matthww9 joins
21:04:20Matthww quits [Ping timeout: 265 seconds]
21:04:20Matthww9 is now known as Matthww
21:56:33Atom joins
22:12:29HP_Archivist quits [Ping timeout: 265 seconds]
22:21:46sec^nd quits [Remote host closed the connection]
22:22:21sec^nd (second) joins
23:07:40IDK quits [Quit: Connection closed for inactivity]