TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

WireGuard: Next Generation Secure Kernel Network Tunnel

118 点作者 psiconaut超过 8 年前

7 条评论

AlyssaRowan超过 8 年前
One comment I&#x27;ll make because it&#x27;s kind of buried in the first paragraph and not really called out: this project is one of the very early adopters of Trevor Perrin&#x27;s state-of-the-art Noise protocol framework design <a href="https:&#x2F;&#x2F;noiseprotocol.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;noiseprotocol.org&#x2F;</a>, so you&#x27;re looking at something <i>dramatically</i> more modern, auditable and (potentially) secure than older, hairier protocols like IPsec, TLSv1.2, OpenVPN, etc.<p>Best of luck, Jason!
dguido超过 8 年前
If you want a reliable VPN you can use today on nearly every platform, try Algo VPN. It uses simplifies using IPSEC so that anyone who can run a few command line scripts can use it.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;trailofbits&#x2F;algo" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;trailofbits&#x2F;algo</a><p>It&#x27;s great that someone is working on what comes next after IPSEC, but the platform support for everyone won&#x27;t come any time soon. If you need a VPN today, Algo is your best answer.
评论 #13573390 未加载
评论 #13571263 未加载
评论 #13571693 未加载
评论 #13571432 未加载
XorNot超过 8 年前
It&#x27;s not clear to me that this really solves any of the UI and management problems associated with VPNs. I&#x27;m sure the new crypto-design is interesting, but exchanging SSH public keys is actually a huge logistical hassle which scales very poorly.<p>The other thing is &quot;container-ready&quot; ... well it just isn&#x27;t. I can use OpenVPN to do the same interface migration trick with a container today. That&#x27;s not the challenge - the challenge is things like managing what happens when the VPN interface goes down and I need to recycle and reconfigure that interface (at which point you end up back at &quot;allocate a private address space, stick the VPN container in a new address space, play with IPTables there to make sure losing the VPN routes doesn&#x27;t mean you start routing over the regular NIC&quot;.
评论 #13572142 未加载
nl超过 8 年前
Speaking of VPNs....<p>Is there a guide somewhere on how to partition applications on Linux so different apps use different VPNs?<p>Obviously the easier way is SSH SOCKS tunnels if the app supports it, but I&#x27;d like a more general method.<p>I believe it is possible by namespacing the apps (or I guess going all the way and containerizing them) and then setting the routing on a per-namespace basis.<p>Is there anywhere this is written down so I don&#x27;t have to spent 6 hours trying to work out how to do it?
评论 #13572957 未加载
评论 #13573603 未加载
评论 #13571754 未加载
评论 #13571838 未加载
dohqu8Zi超过 8 年前
I hope to see a mainline submission for public review of this soon.
sargun超过 8 年前
It seems worrying to me to put something so complicated in the kernel. Perhaps, not even that, but it feels to me as though the fact that this requires in tree changes seems wrong, given the way that networking is going is to enable these network functions via mechanisms such as BPF.
评论 #13571211 未加载
nul_byte超过 8 年前
Can anyone open the slides or video? Using firefox on Fedora and its saying both file types are corrupt.
评论 #13574039 未加载