4 ms·

Good point. Software monoculture is bad though (OpenSSL) and choice is good. That said, I wonder how many crypto libraries are shared between Caddy-SSH and Ope

• francislavoie 5y ago
  > I wonder how many crypto libraries are shared between Caddy-SSH and OpenSSH None, because Caddy-SSH is written in Go, and uses Go stdlib crypto libs which are their own thing. See https://pkg.go.dev/golang.org/x/crypto https://pkg.go.dev/golang.org/x/crypto > Finally, I really hope this is a separate daemon. SSH served by a web server invokes a certain systemd feeling That's entirely up to you. Caddy v2 is designed as an "app platform"; the HTTP app is just one such app that Caddy happens to ship with, but anything else can be plugged in, like an SSH app in this case. You don't have to run both HTTP and SSH in the same process, you could run two instances of Caddy each with their own purpose, if you feel like. https://caddyserver.com/docs/architecture https://caddyserver.com/docs/architecture
• viraptor 5y ago
  Not sure what you mean with systemd. All big parts of it run as separate, locked down processes. But yeah, just for the time when you're hammered with traffic that you want to investigate, you don't want your web server and SSH session to go through the same loop.