Nahum Shalman

> I wasn't aware this was a serious effort, such that I should have sequencing concerns like that. It's been over two years now, so this is mostly your playground....

@zx2c4 please review.

@jwhited your feedback would also be welcome.

Rebased to clear merge conflicts. Still ready for review by @zx2c4.

Closing. Will be integrated into #17

Cool! I have a branch with some code I found where someone else did something similar that I was hacking on but never pushed. I'll take a look at your...

Updated copyright year, added a couple of extra reference links, removed some TODOs that don't actually require action (https://github.com/WireGuard/wireguard-tools/compare/8588ad10c513e50f2b051a4c48ffe33af562a9d5..491d58a4bae08bb74e82a2d372af660ee6d968b6) @zx2c4 This is ready for your review. ~~https://github.com/WireGuard/wireguard-tools/pull/17/commits/491d58a4bae08bb74e82a2d372af660ee6d968b6~~ https://github.com/WireGuard/wireguard-tools/pull/17/commits/77de1e949f7e754b28f5b258c0176718c63741a5 is the...

Bug report from a user: Config file (that works in Linux) with addresses with `/32` appended fail ``` [Interface] ListenPort = 41953 PrivateKey = REDACTED Address = 10.254.254.1/32 [Peer] PublicKey...

That bug should be fixed by my force-push: https://github.com/WireGuard/wireguard-tools/compare/491d58a4bae08bb74e82a2d372af660ee6d968b6..77de1e949f7e754b28f5b258c0176718c63741a5

@zx2c4 please review when you have time. Goes along with wireguard/wireguard-go#39