News for hackers. Stuff that matters.
Re:Security Analysis of WireGuard [pdf] by curiousgal on Saturday September 01, 2018 @04:01AM (#17890820)
I gave up on getting Wireguard to work on an Arch server and an Android client. Algo only supports Ubuntu and *BSD.
Re:Security Analysis of WireGuard [pdf] by smittywerben on Saturday September 01, 2018 @06:47AM (#17891248)
> Algo only supports Ubuntu and *BSD.

Algo, also called Algo VPN, is a separate project which is built on-top of Wireguard [0]. Algo claims to support Android [1].

Wireguard works on Arch and Android [2]. Wireguard for Arch has first class support [3]. Wireguard for Android exists in a forked repository [4].

[0] https://github.com/trailofbits/algo

[1] https://github.com/trailofbits/algo/blob/master/docs/client-...

[2] https://www.wireguard.com/install/

[3] https://wiki.archlinux.org/index.php/WireGuard

[4] https://git.zx2c4.com/wireguard-android

Re:Security Analysis of WireGuard [pdf] by chancecarey on Saturday September 01, 2018 @05:38AM (#17891104)
I use it on Arch with no issues at all.
Re:Security Analysis of WireGuard [pdf] by computerfriend on Saturday September 01, 2018 @10:29AM (#17891986)
Same. I've also set up WireGuard on Ububtu servers and the experience was pretty much identical. Arch doesn't make this any harder.
Re:Security Analysis of WireGuard [pdf] by jonathonf on Saturday September 01, 2018 @05:56AM (#17891145)
Works fine for me on Manjaro using wireguard-dkms and the Wireguard app from the F-Droid store.

Copying public keys back and forth via email seemed a bit of a faff so there's probably a better way. Possibly using `qrencode` would let you set up the client configuration...

Re:Security Analysis of WireGuard [pdf] by curiousgal on Saturday September 01, 2018 @06:18AM (#17891196)
Perhaps I am misunderstanding the premise of Wireguard as all the tutorials seem to be setting up a client and a server that are on the same network, is not possible to have the server as a VPS and have the client connect via the Internet?
Re:Security Analysis of WireGuard [pdf] by linuskendall on Saturday September 01, 2018 @06:32AM (#17891217)
It is really no difference between setting up Wireguard on a local network or via Internet as long as one of the hosts can listen to a public UDP port. If one of your clients are behind a NAT you may need to enable the keep alive option in the client's config
Re:Security Analysis of WireGuard [pdf] by m-p-3 on Saturday September 01, 2018 @07:42PM (#17894512)
Sadly some public networks I had to use were blocking Wireguard, while my IPSec VPN would easily go through each time :(

I wish there was an option to obfuscate the traffic as a plain HTTPS connection, but that would defeat the idea of keeping Wireguard simple.

Re:Security Analysis of WireGuard [pdf] by curiousgal on Saturday September 01, 2018 @07:20AM (#17891339)
My client is indeed behind a NAT. I'll just wait until Wireguard is more mainstream and extremely detailed guides are up.
Re:Security Analysis of WireGuard [pdf] by gnfurlong on Saturday September 01, 2018 @04:49PM (#17893819)
Admittedly, I haven't gotten around to actually using WireGuard yet, but I think it's pretty much as simple as Linuskendall said. https://www.wireguard.com/quickstart/#nat-and-firewall-trave...

Also see this guide on using a public VPS with a Wireguard server to share resources behind two different NAT'd networks: https://staaldraad.github.io/2017/04/17/nat-to-nat-with-wire...