We have enabled Encrypted Client Hello (ECH) on curl on Debian Experimental, for maximum privacy!
https://samueloph.dev/blog/i-use-curl-with-ech-btw-in-debian/
| WEBSITE | https://samueloph.dev |
| GITHUB | https://github.com/samueloph |
| GITLAB | https://salsa.debian.org/samueloph |
| https://www.linkedin.com/in/samueloph/ |
We have enabled Encrypted Client Hello (ECH) on curl on Debian Experimental, for maximum privacy!
https://samueloph.dev/blog/i-use-curl-with-ech-btw-in-debian/
PSA: Did you know that itโs **unsafe** to put code diffs into your commit messages?
Like https://github.com/i3/i3/pull/6564 for example
Such diffs will be applied by patch(1) (also git-am(1)) as part of the code change!
This is how a sleep(1) made it into i3 4.25-2 in Debian unstable.
RE: https://fosstodon.org/@LPI/115741281341184322
I've moved to Seattle just recently due to my job and was lucky enough to meet a long time friend, Jon "maddog" Hall, and Andrew and Ted from @LPI who gave me local tips, especially on where to eat the best dumplings.
The timing was great as I've got to attend a Free Software conference and also meet other Debian Developers right when I moved.
Now I'll be spreading #curl and #wcurl stickers on this side of the world.
After a few hours of mixing, editing, rendering and writing subtitles, I've finally published the last of my talks from DebConf25 (@debian)
"The Security of Debian - An introduction to advanced users - DebConf25 " is a good starting point for those curious about how distributions handle security vulnerabilities and how that's organized outside of the distros.