News for hackers. Stuff that matters.

A comment on Protecting SSH Keys with macOS Secure Enclave. Parent comment

Re:Protecting SSH Keys with macOS Secure Enclave by Barbing on Wednesday November 11, 2026 @01:25AM (#50450288)
>enough friction that none of us did so far.

Emailed per https://news.ycombinator.com/item?id=50450200

Definitely still a bug right? Linked them to your parent comment.

Edit: oops sorry team, think you're on it (4d ago): https://github.com/whyredfire/wireguard-apple/commit/0bac142...

[ Parent | on HN ]
Re:Protecting SSH Keys with macOS Secure Enclave by database64128 on Wednesday November 11, 2026 @01:32AM (#50450327)
> Definitely still a bug right? Linked them to your parent comment.

Thanks! Yes, it is still a bug.

> Edit: oops sorry team, think you're on it (4d ago)

I don't think @zx2c4 has seen this PR, and the author of the PR has not sent a bug report yet, so it's probably fine :P

[ Parent | on HN ]
Re:Protecting SSH Keys with macOS Secure Enclave by Barbing on Wednesday November 11, 2026 @02:13AM (#50450553)
All right! :)
[ Parent | on HN ]
Re:Protecting SSH Keys with macOS Secure Enclave by traceroute66 on Wednesday November 11, 2026 @03:45AM (#50451066)
> Thanks! Yes, it is still a bug.

Its unfortunate no updates for Wireguard macOS have been pushed out for 3 years, App Store is still showing 1.0.16 as the latest version – as also confirmed on the Wireguard website at the latest version.

No doubt macOS APIs have moved on a lot in 3 years and so perhaps bugs that are being seen are simply a reflection of the lack of updates to keep up with API changes ? Just thinking aloud here, I don't know if the concept of OS API changes are applicable to this particular PR / bug.

[ Parent | on HN ]