News for hackers. Stuff that matters.
Re:Protecting SSH Keys with macOS Secure Enclave by BaardFigur on Wednesday November 11, 2026 @07:05AM (#50452453)
I'm using WireGuard myself. Not on MacOS, but on Windows/Linux/Android. The reason I went with WireGuard to begin with, is due to how secure it suppsedly was. Having long standing unresolved issues like that is a bit worrying. I'm still most likely safe, but it's not exactly reassuring, either
Re:Protecting SSH Keys with macOS Secure Enclave by megous on Wednesday November 11, 2026 @08:03AM (#50452918)
This is likely just that if someone chooses an OS that requires a special HW just to build a release with no easy cross-compilation possible, and to pay a gatekeeper just to publish it, and that can't even run on an emulated computer properly, they can't expect FOSS maintainers will be bothered with much more than "here's a source code, build it/test it/do QA yourself if you like" for their particular pet platform.
Re:Protecting SSH Keys with macOS Secure Enclave by dboreham on Wednesday November 11, 2026 @08:26AM (#50453140)
Best common on HN this week.
Re:Protecting SSH Keys with macOS Secure Enclave by blackcatsec on Wednesday November 11, 2026 @11:57AM (#50455631)
Just going to reply to your comment here: the choice to use wireguard shouldn't come down to relative security (although I guess it gets a benefit here), but from being fast and simplistic.

All of the traditional components of VPN management are removed from the core code. Wireguard follows the model "do one thing, and do it well." It's also built into the kernel, which inherently can make it faster than userland VPN software.

This is why companies like Tailscale exist--as they're basically selling back the features that you would get in a more traditional IPSEC VPN, but in front of Wireguard instead.