We don't pin those comments to the top because it would nudge the conversation in too meta a direction. It's better that they hover partway down the page.
What I do is ctrl+F 'ycombinator' on the thread before posting one, though of course that doesn't avoid race conditions.
"[..] a security bug identified by
AI tools is subsequently independently discovered by a different
researcher. This suggests that adversaries who do not report bugs
to OSS projects are likely to be able to discover these bugs too.
Given this, the OpenSSH team will, for now, be making more frequent
releases to get bugfixes into users' hands more quickly rather than
batching them until the next planned release."
wireplug lets you create mesh VPNs using standard WireGuard.
Your wg config files stay almost the same, except you no longer have to specify an `Endpoint` for your peers.
Instead, wireplug detects all your possible endpoints (including LAN) and coordinates them with your peers for you.
It handles NAT traversal and works with the in-kernel WireGuard driver on Linux and OpenBSD.
This lets you keep managing your own keys and network topology, while also maintaining connectivity when moving between networks.
Currently working on improving NAT traversal by adding support for PCP and NAT-PMP.
I continue working on https://wireplug.org: A simple, free, and open source connectivity coordinator for WireGuard. Basically a way to keep WireGuard tunnels connected while moving between different access points. It handles (basic) NAT traversal and works with the in-kernel WireGuard driver on Linux and OpenBSD. You can find the technical details at https://wireplug.org
For anyone wondering: AF_ALG is a Linux socket interface that exposes the kernel’s crypto API via file descriptors, using normal read(2)/write(2) calls for hashing and encryption.
It's already a configurable option in the kernel which can be fully disabled by distros if they wanted to provide their own compatibility layer, or just not ship any software that has a hard dependency on it.
It feels like they did everything they could so that the cheap MacBook with an iPhone CPU would not be lighter than the 1.5x more expensive MacBook with Apple Silicon
Thank you, from my cursory look of their comparison page, this is the information that was missing. But maybe that was a deliberate choice on Apple's part.
previous discussions:
- https://news.ycombinator.com/item?id=25136422
- https://news.ycombinator.com/item?id=32035054
- https://news.ycombinator.com/item?id=40103590