From: Joe Blue <joeblew99@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: golang implemenation
Date: Fri, 17 Mar 2017 12:33:19 +0000 [thread overview]
Message-ID: <CAGhajTJG2gkyUjs8xmV=zYj_=tPjefHJ70mhnn9RALeC_bXY1w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
Hey,
Wireguard looks really good and i read that golang / rust implemenations
were planned.
I looked the git tree and there is only one file, so i am was wondering
what the current intent is towards a golang port.
Part of the reason for being keen on a golang port is:
- Can run the server with just a linuxkernel and golang code and nothing
else to lower attack surface. For example of this see.
https://gokrazy.github.io/
- Can run clients on desktops and mobile very easily with golang. With
existing VPN clients its highly fragmented and so a cleint and server all
in golang really makes it easier to get going IMHO.
Please let me knwo the status, intent and how i can help.
Regards
Joe
[-- Attachment #2: Type: text/html, Size: 985 bytes --]
next reply other threads:[~2017-03-17 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 12:33 Joe Blue [this message]
2017-03-17 12:34 ` Jason A. Donenfeld
2017-03-17 13:53 ` Joe Blue
2017-03-29 5:49 ` James Tucker
2017-03-29 7:13 ` Joe Blue
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGhajTJG2gkyUjs8xmV=zYj_=tPjefHJ70mhnn9RALeC_bXY1w@mail.gmail.com' \
--to=joeblew99@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).