News for hackers. Stuff that matters.
Re:WireGuard: next generation in-kernel modern VPN by Aissen on Tuesday June 28, 2016 @11:25AM (#11994487)
Yes, guilty as charged. Ever since I saw you presentation in Paris in last September, I was dying for wireguard to come out.

I'm curious what will be your strategy with regard to working or not with upstream Linux ?

Re:WireGuard: next generation in-kernel modern VPN by zx2c4 on Tuesday June 28, 2016 @11:29AM (#11994522)
Oh cool you came to the kernel recipes talk. Much has progressed since then.

I wrote an email on LKML and netdev today to David Miller, the network subsystem maintainer. It's not ready for a [PATCH] set now, but it is ready to get initial feedback from them, so that I can start to get things ready for upstreaming. So: that's on the roadmap and a primary objective!

Re:WireGuard: next generation in-kernel modern VPN by runejuhl on Wednesday June 29, 2016 @02:41AM (#11999905)
For those of you who're interested, the mail to LKML can be found here: https://lkml.org/lkml/2016/6/28/629
Re:WireGuard: next generation in-kernel modern VPN by loeg on Tuesday June 28, 2016 @02:56PM (#11996465)
Would you mind dual-licensing under a more permissive license (BSD or MIT) so the work can be included in the BSD family of operating systems as well as Linux?
Re:WireGuard: next generation in-kernel modern VPN by zx2c4 on Tuesday June 28, 2016 @05:04PM (#11997570)
I answered this question elsewhere. The answer is that - probably, why not? I need to think about it for more than a few seconds. But the only reason I chose GPLv2 is because that's what Linux uses. I'll quit being lazy and think more carefully about licenses, and hopefully we'll wind up with something good for the BSDs.
Re:WireGuard: next generation in-kernel modern VPN by pdimitar on Wednesday June 29, 2016 @07:24AM (#12000869)
I am not a lawyer but in my eyes having a BSD/MIT license will also save you from a corporation "adopting" your technology and sue you afterwards for infringing a super vague patent of theirs... or something along the lines.

If your work is in the public domain, then at least the corporations would have much harder time hijacking and wall-garden it, and the chances of them simply giving up are higher. Or so I hope.

I've read a good chunk of your website. GREAT WORK! Do not give up, you're doing next-level work. =)

Re:WireGuard: next generation in-kernel modern VPN by loeg on Wednesday June 29, 2016 @01:19PM (#12003091)
Yeah, you're not a lawyer. This is nonsensical gibberish.
Re:WireGuard: next generation in-kernel modern VPN by pdimitar on Thursday June 30, 2016 @01:19PM (#12010096)
The corporations haven't really left us with good impressions in the last 15 years though, did they?

If I learned anything from those last 15 years is that they'll sue you if you don't agree the Moon is made of cheese if it suits their agenda.

So I remain cynical towards them. If they can hijack a good technology for their own profit, they will do it. I think we all knew that much at this point?

Re:WireGuard: next generation in-kernel modern VPN by gcb0 on Wednesday June 29, 2016 @07:43AM (#12000955)
is this really a thing?
Re:WireGuard: next generation in-kernel modern VPN by pdimitar on Thursday June 30, 2016 @01:21PM (#12010109)
As I pointed out, I am not a lawyer. I have however read news vaguely similar to what I described, many times through the years. It really makes me fearful that in the end you're vulnerable just for publishing your work...

I do hope I am very naively wrong. But history hasn't given us much comfort in this area so far.

Re:WireGuard: next generation in-kernel modern VPN by loeg on Tuesday June 28, 2016 @08:31PM (#11998679)
Thanks for considering it! For what it's worth, there is dual BSD/GPL precedent in various places in Linux (e.g., most of the drm GPU drivers, NTB, etc).
Re:WireGuard: next generation in-kernel modern VPN by ciokan on Tuesday June 28, 2016 @11:33AM (#11994567)
Can I bind it to external ip addresses and give a certain user an outgoing (or even private ips that I can then forward) address I chose? Don't know if my question makes sense but I'm interested in routing a certain user to a certain ip every time he/she connects.
Re:WireGuard: next generation in-kernel modern VPN by zx2c4 on Tuesday June 28, 2016 @11:35AM (#11994577)
WireGuard as a simple associations between public keys and each public keys list of allowed IPs. Within this structure, it seems like you should be able to do what you want.