3 ms·

Or you could just use memory-safe OpenSSL. https://github.com/pizlonator/deluded-openssl-3.2.0 https://github.com/pizlonator/deluded-openssl-3.2.0 It's based

Or you could just use memory-safe OpenSSL. https://github.com/pizlonator/deluded-openssl-3.2.0 https://github.com/pizlonator/deluded-openssl-3.2.0 It's based on Fil-C https://github.com/pizlonator/llvm-project-deluge/blob/deluge/Manifesto.md https://github.com/pizlonator/llvm-project-deluge/blob/delug... There's no unsafe code in it. The whole thing is recompiled with Fil-C. Works well enough that I can run a memory-safe curl and a memory-safe ssh.

bradfitz 3y ago
"On the other hand, Fil-C is quite slow. It's 200x slower than legacy C right now. "
- pizlonator 3y ago
  It's slow for good reasons, like ensuring that I have a super reliable compiler that lets me port a lot of stuff without dealing with miscompiles. Fil-C will be fast, don't worry. (The manifesto enumerates the hilarious reasons for the slowness. If you had read that, you probably wouldn't have cited the 200x.)
senkora 3y ago
This is legitimately very interesting but I can't help but notice that every single one of your commit messages is either "more shit" or a misspelling thereof: https://github.com/pizlonator/deluded-openssl-3.2.0/commits/master/ https://github.com/pizlonator/deluded-openssl-3.2.0/commits/...
- pizlonator 3y ago
  So?