| 4 Jan 2022 |
 Samantaz Fox | make RELEASE=0 DISABLE_QUIC=1
| 00:50:03 |
 RSS (bot) |
New commit to Invidious: Also fix DISABLE_QUIC declaration
| 00:51:20 |
 zehka | In reply to @samantazfox:pussthecat.org
zehka you can try again to compile without QUIC (using latest master) Ok, thank you. I'll try that tomorrow. | 00:51:39 |
| Samantaz Fox | sure ^^ | 00:54:01 |
|  mrckndt joined the room. | 01:47:13 |
| mrckndt left the room. | 01:47:25 |
|  byteskeptical left the room. | 08:13:47 |
 TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
I really feel the cheapness of this VPS xD Ahah sorry xD | 10:46:27 |
|  tinytoas1 joined the room. | 11:11:15 |
| Samantaz Fox | TheFrenchGhosty don't be ^^ | 12:44:38 |
| Samantaz Fox | Btw, you can shut down the VPS | 12:45:15 |
| Samantaz Fox | I don't need it anymore | 12:45:21 |
| TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
I don't need it anymore The problem is solved? Or just QUIC? | 13:13:53 |
| Samantaz Fox | the problem can't really be solved | 13:14:16 |
| zehka | I recompiled it without quic and it seems to be running, so it seems to be a QUIC issue | 13:14:30 |
| Samantaz Fox | on those distros, compiling without QUIC is required | 13:14:30 |
| TheFrenchGhosty | In reply to @samantazfox:pussthecat.org
on those distros, compiling without QUIC is required There's no way around it? What's the issue? | 13:15:28 |
| Samantaz Fox | zehka yeah. This is because QUIC requires a modified version of openSSL to run. lsquic (the library we use) uses BoringSSL, the Google fork of openSSL that supports QUIC | 13:15:59 |
|  NeoCode joined the room. | 13:16:33 |
| Samantaz Fox | And because of that, the linker uses BoringSSL rather than the system's openSSL for the Crystal standard library (HTTP::Client) | 13:16:50 |
| zehka | But wait a minute: The disable_lsquic switch didn't work because it should have been disable_quic, right? | 13:17:22 |
| Samantaz Fox | yeaaaah xD | 13:17:32 |
| Samantaz Fox | typo on my side | 13:17:39 |
| zehka | But why did it work then with the symlink? | 13:17:58 |
| Samantaz Fox | As I said, you have to almost identical libraries with the same API : BoringSSL, which is modified to support QUIC, and the system's openSSL, which may be modified too | 13:19:11 |
| Samantaz Fox | The default is to look into /etc/ssl/ for certificates. OpenSSL on Debian, Ubuntu, etc.. and BoringSSL do that | 13:20:06 |
| Samantaz Fox | but the openSSL version shipped with ArmaLinux has been modified so it looks inside /etc/pki | 13:20:44 |
| Samantaz Fox | Ideally, we'd want to have the two libraries separate (BoringSSL only for the QUIC client, and the system's OpenSSL for the rest) | 13:21:55 |
| TheFrenchGhosty | So it's possible to fix it? | 13:22:19 |
| Samantaz Fox | Idk. I'd have to dig into it. One thing I'm sure is that BoringSSL's symbols (which are used by the linker to "connect" libraries) should be stripped. | 13:23:45 |
