Newest at the top
| 2025-01-22 06:31:15 +0100 | <probie> | geekosaur: It's no security panacea, but it still reduces the number of parties you need to trust |
| 2025-01-22 06:28:12 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
| 2025-01-22 06:25:38 +0100 | <geekosaur> | that's just one way to do it. the one I described above is another. there are a lot of exploits possible; RoTT isn't about a single specific form of exploit but the entire class. it uses the specific one as an example |
| 2025-01-22 06:23:18 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 06:23:15 +0100 | <mange> | Isn't the point of "reflections on trusting trust" that the exploit survives in the binary alone? Bootstrapping at least ensures we can find the exploit in source, eventually. |
| 2025-01-22 06:16:10 +0100 | tnt2 | tnt1 |
| 2025-01-22 06:16:10 +0100 | tnt1 | (~Thunderbi@user/tnt1) (Ping timeout: 272 seconds) |
| 2025-01-22 06:16:04 +0100 | tnt2 | (~Thunderbi@user/tnt1) tnt1 |
| 2025-01-22 06:15:15 +0100 | <geekosaur> | (so you're going to vet patches. (a) damn lot of patches in something as old as gcc; (b) Alice strings together 30 patches, each innocuous but together you get the xz exploit. Will you catch that?) |
| 2025-01-22 06:12:21 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-22 06:11:55 +0100 | <geekosaur> | I have to say I still don't see the point. The only thing I can think of is vetting the entire build chain, but the xz exploit demonstrated that "Reflections on Trusting Trust" is still with us and only gets worse with every new link in the chain |
| 2025-01-22 06:07:56 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 06:06:08 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 252 seconds) |
| 2025-01-22 06:06:07 +0100 | <jackdk> | MicroHs will be buildable from Hugs, meaning that we have at least one actively developed Haskell compiler that's bootstrappable from C, which means you could if you wanted root its bootstrap chain in hex0, the couple-hundred-byte assembler |
| 2025-01-22 06:01:43 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-22 05:58:48 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-22 05:54:19 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 05:43:44 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2025-01-22 05:38:57 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 05:38:45 +0100 | <haskellbridge> | <sm> sounds cool, what will it mean ? |
| 2025-01-22 05:35:58 +0100 | <homo> | exciting good news https://github.com/augustss/MicroHs/tree/hugs |
| 2025-01-22 05:34:01 +0100 | halloy1022 | (~halloy102@111.65.75.121) (Remote host closed the connection) |
| 2025-01-22 05:33:47 +0100 | halloy1022 | (~halloy102@111.65.75.121) |
| 2025-01-22 05:33:15 +0100 | agent314 | (~quassel@208.131.130.69) agent314 |
| 2025-01-22 05:28:38 +0100 | <geekosaur> | ghc was done with its delay when the first line came out |
| 2025-01-22 05:28:18 +0100 | <geekosaur> | most of the slowdown there, though, was lambdabot throttling so it didn't get kicked for flooding… |
| 2025-01-22 05:28:00 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-22 05:27:45 +0100 | <monochrom> | But yeah it's exponential length output so exponential time so we're cool. :) |
| 2025-01-22 05:23:34 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 05:20:36 +0100 | aforemny_ | (~aforemny@2001:9e8:6cc6:4600:1315:1249:75e2:82ec) (Ping timeout: 276 seconds) |
| 2025-01-22 05:19:58 +0100 | <jle`> | oh sorry i didn't realize that would actually evaluate |
| 2025-01-22 05:19:54 +0100 | <lambdabot> | b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))))))) |
| 2025-01-22 05:19:52 +0100 | <lambdabot> | (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b))))), (((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, |
| 2025-01-22 05:19:50 +0100 | <lambdabot> | b))))), (((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))))), ((((((b, b), (b, b)), ((b, b), |
| 2025-01-22 05:19:50 +0100 | <lambdabot> | b))), (((b, b), (b, b)), ((b, b), (b, b))))))), (((((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, |
| 2025-01-22 05:19:50 +0100 | <lambdabot> | b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b))))), (((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, |
| 2025-01-22 05:19:50 +0100 | <lambdabot> | b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))))), ((((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, |
| 2025-01-22 05:19:50 +0100 | <lambdabot> | b -> ((((((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b)))), ((((b, b), (b, b)), ((b, b), (b, b))), (((b, b), (b, b)), ((b, b), (b, b))))), (((((b, b), (b, b)), ((b, b), (b, |
| 2025-01-22 05:19:49 +0100 | <jle`> | :t let f x = (x, x) in f . f . f . f . f . f . f . f |
| 2025-01-22 05:19:45 +0100 | aforemny | (~aforemny@2001:9e8:6ce4:b500:6e75:95aa:3ce2:b258) aforemny |
| 2025-01-22 05:19:01 +0100 | homo | (~homo@user/homo) homo |
| 2025-01-22 05:18:47 +0100 | dysthesis | (~dysthesis@user/dysthesis) (Remote host closed the connection) |
| 2025-01-22 05:18:43 +0100 | <jle`> | tuple trees are basically type-level trees -- there's that common trick that you can use them to easily overload/timeout typechecking |
| 2025-01-22 05:15:17 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 248 seconds) |
| 2025-01-22 05:12:35 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-22 05:10:59 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-01-22 05:08:34 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds) |
| 2025-01-22 05:08:12 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-22 05:05:52 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-01-22 05:05:37 +0100 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |