<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">what is the go and rust git uri?<br><br><div id="AppleMailSignature"><span style="font-size: 13pt;">Thomas J Munn</span><br><div><div><br></div></div></div><div><br>On Mar 5, 2018, at 06:00, <a href="mailto:wireguard-request@lists.zx2c4.com">wireguard-request@lists.zx2c4.com</a> wrote:<br><br></div><blockquote type="cite"><div><span>Send WireGuard mailing list submissions to</span><br><span> <a href="mailto:wireguard@lists.zx2c4.com">wireguard@lists.zx2c4.com</a></span><br><span></span><br><span>To subscribe or unsubscribe via the World Wide Web, visit</span><br><span> <a href="https://lists.zx2c4.com/mailman/listinfo/wireguard">https://lists.zx2c4.com/mailman/listinfo/wireguard</a></span><br><span>or, via email, send a message with subject or body 'help' to</span><br><span> <a href="mailto:wireguard-request@lists.zx2c4.com">wireguard-request@lists.zx2c4.com</a></span><br><span></span><br><span>You can reach the person managing the list at</span><br><span> <a href="mailto:wireguard-owner@lists.zx2c4.com">wireguard-owner@lists.zx2c4.com</a></span><br><span></span><br><span>When replying, please edit your Subject line so it is more specific</span><br><span>than "Re: Contents of WireGuard digest..."</span><br><span></span><br><span></span><br><span>Today's Topics:</span><br><span></span><br><span> 1. [ANNOUNCE] WireGuard Snapshot `0.0.20180304` Available</span><br><span> (Jason A. Donenfeld)</span><br><span> 2. Tunsafe Windows client for wireguard (not opensource yet they</span><br><span> say (Henrique Carrega)</span><br><span> 3. Re: Tunsafe Windows client for wireguard (not opensource yet</span><br><span> they say (Jason A. Donenfeld)</span><br><span></span><br><span></span><br><span>----------------------------------------------------------------------</span><br><span></span><br><span>Message: 1</span><br><span>Date: Sun, 04 Mar 2018 18:54:23 +0100</span><br><span>From: "Jason A. Donenfeld" <<a href="mailto:Jason@zx2c4.com">Jason@zx2c4.com</a>></span><br><span>To: "WireGuard mailing list" <<a href="mailto:wireguard@lists.zx2c4.com">wireguard@lists.zx2c4.com</a>></span><br><span>Subject: [ANNOUNCE] WireGuard Snapshot `0.0.20180304` Available</span><br><span>Message-ID: <<a href="mailto:b97b4ced2749b831@frisell.zx2c4.com">b97b4ced2749b831@frisell.zx2c4.com</a>></span><br><span>Content-Type: text/plain; charset=UTF-8</span><br><span></span><br><span>-----BEGIN PGP SIGNED MESSAGE-----</span><br><span>Hash: SHA256</span><br><span></span><br><span>Hello,</span><br><span></span><br><span>A new snapshot, `0.0.20180304`, has been tagged in the git repository.</span><br><span></span><br><span>Please note that this snapshot is, like the rest of the project at this point</span><br><span>in time, experimental, and does not consitute a real release that would be</span><br><span>considered secure and bug-free. WireGuard is generally thought to be fairly</span><br><span>stable, and most likely will not crash your computer (though it may).</span><br><span>However, as this is a pre-release snapshot, it comes with no guarantees, and</span><br><span>its security is not yet to be depended on; it is not applicable for CVEs.</span><br><span></span><br><span>With all that said, if you'd like to test this snapshot out, there are a</span><br><span>few relevent changes.</span><br><span></span><br><span>== Changes ==</span><br><span></span><br><span> * NOTICE: off the grid</span><br><span></span><br><span> Do note that I'll be going off the grid from the end of this coming week until</span><br><span> April 1. This snapshot is expected to be fairly stable in the interim.</span><br><span></span><br><span> * queueing: skb_reset: mark as xnet</span><br><span></span><br><span> This allows cgroups to classify packets.</span><br><span></span><br><span> * contrib: embedded-wg-library: add ability to add and del interfaces</span><br><span> * contrib: embedded-wg-library: add key generation functions</span><br><span></span><br><span> The embeddable library gains a few extra tricks, for people implementing</span><br><span> plugins for various network managers.</span><br><span></span><br><span> * crypto: read only after init</span><br><span> * allowedips: fix comment style</span><br><span> * messages: MESSAGE_TOTAL is unused</span><br><span> * global: in gnu code, use un-underscored asm</span><br><span> * noise: fix function prototype</span><br><span></span><br><span> Small cleanups.</span><br><span></span><br><span> * compat: workaround netlink refcount bug</span><br><span></span><br><span> An upstream refcounting bug meant that in certain situations it became</span><br><span> impossible to unload the module. So, we work around it in the compat code. The</span><br><span> problem has been fixed in 4.16.</span><br><span></span><br><span> * contrib: keygen-html: rewrite in pure javascript</span><br><span> * Revert "contrib: keygen-html: rewrite in pure javascript"</span><br><span></span><br><span> We nearly moved away from emscripten'ing the fiat32 code, but the resultant</span><br><span> floating point javascript was just too terrifying.</span><br><span></span><br><span> * Kconfig: require DST_CACHE explicitly</span><br><span></span><br><span> Required for certain frankenkernels.</span><br><span></span><br><span> * compat: use correct -include path</span><br><span></span><br><span> Fixes certain out-of-tree build systems.</span><br><span></span><br><span> * noise: align static_identity keys</span><br><span></span><br><span> Gives us better alignment of private keys.</span><br><span></span><br><span> * wg-quick: if resolvconf/interface-order exists, use it</span><br><span> * wg-quick: if resolvconf/run/iface exists, use it</span><br><span></span><br><span> Better compatibility with Debian's resolvconf.</span><br><span></span><br><span> * contrib: add extract-handshakes kprobe example</span><br><span></span><br><span> Small utility for extracting ephemeral key data from the kernel's memory. More</span><br><span> information can be found here:</span><br><span> <a href="https://lists.zx2c4.com/pipermail/wireguard/2018-February/002439.html">https://lists.zx2c4.com/pipermail/wireguard/2018-February/002439.html</a></span><br><span></span><br><span>As always, the source is available at <a href="https://git.zx2c4.com/WireGuard/">https://git.zx2c4.com/WireGuard/</a> and</span><br><span>information about the project is available at <a href="https://www.wireguard.com/">https://www.wireguard.com/</a> .</span><br><span></span><br><span>This snapshot is available in tarball form here:</span><br><span> <a href="https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180304.tar.xz">https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20180304.tar.xz</a></span><br><span> SHA2-256: efb1652f0da67fb2731040439b6abb820a5e2f1bc177aa15c5dce68ea3327787</span><br><span> BLAKE2b-256: 9b49122b546d334a431b12e5b62582a094db737f2497652e55b4155709107c40</span><br><span></span><br><span>If you're a snapshot package maintainer, please bump your package version. If</span><br><span>you're a user, the WireGuard team welcomes any and all feedback on this latest</span><br><span>snapshot.</span><br><span></span><br><span>Finally, WireGuard development thrives on donations. By popular demand, we</span><br><span>have a webpage for this: <a href="https://www.wireguard.com/donations/">https://www.wireguard.com/donations/</a></span><br><span></span><br><span>Thank you,</span><br><span>Jason Donenfeld</span><br><span></span><br><span></span><br><span>-----BEGIN PGP SIGNATURE-----</span><br><span></span><br><span>iQJEBAEBCAAuFiEEq5lC5tSkz8NBJiCnSfxwEqXeA64FAlqcMrsQHGphc29uQHp4</span><br><span>MmM0LmNvbQAKCRBJ/HASpd4DrndND/0ZkzKOnLdYS6NNX+qvdKhwQ4XeOznqAOEo</span><br><span>22z9T/4NalrDe5X8I7LWIwN65KVpcGvoghi5AHI0k4QMGLwdtth+W5beLVhY/U6P</span><br><span>iS2TtdC/5Tp4ovP2ohRn+Ckz6fAP3d+TrV8YWnXi17zrGYjFXXGXSHI98C589Syz</span><br><span>FHyYB1Q1YiGB96wilYCdV+uc23esTTenUQudq/KwJV71I7XpuFVKAZ9uWli/1Jv1</span><br><span>HOk0TTglxDA3orqtPNP1WHxVuKasktvBy4MPNg3B2Ilbdvsmf3cuta1Pyr5ulX47</span><br><span>QwIlr+D+xBFeIbQVYQZsY5eqv6dvAbRcgvZnsxjTohO3X+9s3JTIoPkB+qssiSkT</span><br><span>yP9zhe7JRbLGd6Y+Ys68tKEJQAEtLnGqduj4Lwe0vfcMZ9ItlcsCG4ICxhSrbyIR</span><br><span>F3zKrVlVypWgwjzHOoa8jg7+XEzRfnTAoYHZLxRdV5oB3yQFXn+a41HNZF9BQl00</span><br><span>65g9A5pBDxkcbiwkT884GtAt+bekbFSvb8+bYr0LgbgIt7DAW5z+fe09mlATv3W/</span><br><span>uJpateTM7irm8O3BDvxUh+GGIIqKMNbteUX8nRcPLwMqtJpgC5GCvocjbfJRXIt2</span><br><span>IwnYYPzvQfyDZz5HPQaaXmIInF+EZFBC310tCkwKk5T72+/+zJuGmMjF4EayplrG</span><br><span>SGQYvER10Q==</span><br><span>=LTAE</span><br><span>-----END PGP SIGNATURE-----</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 2</span><br><span>Date: Mon, 5 Mar 2018 08:26:23 +0000</span><br><span>From: Henrique Carrega <<a href="mailto:hcarrega@gmail.com">hcarrega@gmail.com</a>></span><br><span>To: <a href="mailto:wireguard@lists.zx2c4.com">wireguard@lists.zx2c4.com</a></span><br><span>Subject: Tunsafe Windows client for wireguard (not opensource yet they</span><br><span> say</span><br><span>Message-ID: <<a href="mailto:41222FCF-F9F5-4FEC-AA71-73C48F4DA4BA@gmail.com">41222FCF-F9F5-4FEC-AA71-73C48F4DA4BA@gmail.com</a>></span><br><span>Content-Type: text/plain; charset="us-ascii"</span><br><span></span><br><span><a href="https://tunsafe.com/">https://tunsafe.com/</a></span><br><span></span><br><span><a href="https://reddit.com/r/VPN/comments/82183o/tunsafe_a_high_performance_wireguard_vpn_client/">https://reddit.com/r/VPN/comments/82183o/tunsafe_a_high_performance_wireguard_vpn_client/</a></span><br><span>Sent from my iPhone</span><br><span>-------------- next part --------------</span><br><span>An HTML attachment was scrubbed...</span><br><span>URL: <<a href="http://lists.zx2c4.com/pipermail/wireguard/attachments/20180305/e7c2813d/attachment-0001.html">http://lists.zx2c4.com/pipermail/wireguard/attachments/20180305/e7c2813d/attachment-0001.html</a>></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Message: 3</span><br><span>Date: Mon, 5 Mar 2018 10:19:35 +0100</span><br><span>From: "Jason A. Donenfeld" <<a href="mailto:Jason@zx2c4.com">Jason@zx2c4.com</a>></span><br><span>To: Henrique Carrega <<a href="mailto:hcarrega@gmail.com">hcarrega@gmail.com</a>></span><br><span>Cc: WireGuard mailing list <<a href="mailto:wireguard@lists.zx2c4.com">wireguard@lists.zx2c4.com</a>></span><br><span>Subject: Re: Tunsafe Windows client for wireguard (not opensource yet</span><br><span> they say</span><br><span>Message-ID:</span><br><span> <<a href="mailto:CAHmME9r95cjSXK8YitGuHxFp0EfrMKhQEGXL5Ux=rMXLt=U5FA@mail.gmail.com">CAHmME9r95cjSXK8YitGuHxFp0EfrMKhQEGXL5Ux=rMXLt=U5FA@mail.gmail.com</a>></span><br><span>Content-Type: text/plain; charset="UTF-8"</span><br><span></span><br><span>Hi Henrique,</span><br><span></span><br><span>Thanks for posting this.</span><br><span></span><br><span>Please stay away from this software, and generally be wary of</span><br><span>closed-source WireGuard implementations trying to fill the void. This</span><br><span>one was written by a community-unfriendly proprietary author, and</span><br><span>we've got little way of ensuring protocol compliance or basic</span><br><span>security. Especially from my discussions from him, it's clear what</span><br><span>he's up to, and this seems like some nastiness. Should I spend my time</span><br><span>reverse engineering this software and discovering zero-days? Probably</span><br><span>not a good use of my time, despite my usual love of this sort of</span><br><span>thing.</span><br><span></span><br><span>One aspect of the WireGuard project is that we're taking development</span><br><span>very carefully and slowly, not jumping to premature releases, and</span><br><span>really studying every bit of what we produce in order to ship the</span><br><span>least-vulnerable and most-correct code we possibly can. We're still</span><br><span>shipping code -- it's not an approach that results in a complete</span><br><span>standstill -- but it does mean that in these intervening periods,</span><br><span>there will be propheteers and cowboys coming out of the woodwork to</span><br><span>fill the void.</span><br><span></span><br><span>It's quite easy to make a tiny tunneling protocol that's reasonably</span><br><span>fast and does a few things; if you look on Github there are hundreds.</span><br><span>It's quite another thing to write robust and secure software intend to</span><br><span>last for a long time. That's what we're working on here.</span><br><span></span><br><span>Fortunately we have two very nice projects that are rapidly</span><br><span>approaching maturity: one in Go and one in Rust. I fully welcome</span><br><span>future OSS authors into the project. When I'm back from visiting</span><br><span>family at the beginning of April, I think we'll be in a good place to</span><br><span>have a few first releases.</span><br><span></span><br><span>I'll also do what I can to see that people aren't peddling junk and</span><br><span>calling it wireguard, so as to reduce user confusion, but this of</span><br><span>course isn't a very easy endeavor. I'm open to suggestions on how to</span><br><span>approach this.</span><br><span></span><br><span>Regards,</span><br><span>Jason</span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>Subject: Digest Footer</span><br><span></span><br><span>_______________________________________________</span><br><span>WireGuard mailing list</span><br><span><a href="mailto:WireGuard@lists.zx2c4.com">WireGuard@lists.zx2c4.com</a></span><br><span><a href="https://lists.zx2c4.com/mailman/listinfo/wireguard">https://lists.zx2c4.com/mailman/listinfo/wireguard</a></span><br><span></span><br><span></span><br><span>------------------------------</span><br><span></span><br><span>End of WireGuard Digest, Vol 24, Issue 4</span><br><span>****************************************</span><br></div></blockquote></body></html>