Damien MillerOct 21

I really do like Golang being "batteries included".

It took only a few hours to write a moderately featureful TLS-terminating reverse HTTP proxy that used nothing outside the built-in libraries.

The only compromise was using JSON for the configuration file. I would have preferred textproto…

Show threadDamien MillerOct 21
The proxy does PQ key agreement by default (MLKEM768X25519) and I'm not concerned about supply-chain risk as I would be if I had to navigate a bunch of third-party packages
Show threadAmanda
@damienmiller that’s really cool. What are you using to do TLS?
Oct 21 at 9:02amWeb
Show threadDamien MillerOct 21
@amanda yeah, it's in front of some http servers
Show threadDamien MillerOct 21
@amanda err misread your question - just the standard Go crypto/tls library
Show threadAmandaOct 21
@damienmiller Nice, that's very batteries included. Do you know if it's all native Go or if it links to platform backend libraries?
Show threadDamien MillerOct 21
@amanda AFAIK it's all pure go. I think the crypto stuff used to link to system libcrypto but no longer does. @filippo would probably know for sure
Show threadFilippo ValsordaOct 22
@damienmiller @amanda always been pure Go! The original libraries were written by Adam Langley before Go 1.
Show threadAmandaOct 22

@filippo @damienmiller cool! This stands out to me as someone used to the Rust ecosystem, which is much less batteries included and, crucially, often has terrible dynamic linking issues with platform-dependent SSL libraries in particular.

In general I’m very impressed with Go’s ability to produce binaries that run wherever.