News for hackers. Stuff that matters.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by jchook on Wednesday May 29, 2019 @01:10AM (#20037003)
Gotta say, if you just want a VPN to work now, definitely check out Algo or Streisand.

You can get a VPN running in an hour or less. Algo even supports wireguard.

I currently have two VPNs — Algo Wireguard & iVPN.

Anecdotally the wireguard VPN rocks— crazy fast in every way, including connection/disconnection.

Sometimes YouTube is slow.. I just hop on WG and it’s fast again. I’ve achieved faster downloads via WG than my bare internet connection (thanks Linode!)

However, some points to consider:

1. If you use a VPS to host your own VPN.. you don’t gain privacy. Usually your IP can (mostly) still identify you. And your VPS company will hold you accountable for your traffic eg DMCA.

2. OpenVPN never borks my resolv.conf but Wireguard often leaves my DNS resolution in a state of confusion.

Re:Wireguard-docs: Setup, usage, configuration, and a full e... by oarsinsync on Wednesday May 29, 2019 @06:51AM (#20038634)
> 1. If you use a VPS to host your own VPN.. you don’t gain privacy. Usually your IP can (mostly) still identify you. And your VPS company will hold you accountable for your traffic eg DMCA.

Unfortunately, the same can be said for your VPN provider, depending on the provider. They can (and more than one does) save your name, address, billing details, as well as your source IP, and which IP and source ports you appear as after VPN translation has occurred.

Even if they don't do this, traffic analysis by the underlying network provider can de-anonymise your VPN'd traffic from your original source traffic too, and it doesn't take a genius to do this either.

Re:Wireguard-docs: Setup, usage, configuration, and a full e... by 3xblah on Wednesday May 29, 2019 @04:02AM (#20037746)
"2. OpenVPN never borks my resolv.conf but Wireguard often leaves my DNS resolution in a state of confusion."

Checking the source... excerpt from src/tools/wg-quick/openbsd.bash:

   set_dns() {
   [[ ${#DNS[@]} -gt 0 ]] || return 0
   # TODO: this is a horrible way of doing it. Has OpenBSD no resolvconf?
   cmd cp /etc/resolv.conf    "/etc/resolv.conf.wg-quick-backup.$INTERFACE"
   cmd printf 'nameserver %s\n' "${DNS[@]}" >    /etc/resolv.conf
   }
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by zx2c4 on Wednesday May 29, 2019 @04:41AM (#20037972)
We're doing something better on other platforms. But for OpenBSD I'm not entirely sure the best way. Suggestions welcome.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by Hello71 on Wednesday May 29, 2019 @07:42AM (#20038916)
did you check what openvpn does? I would assume they have something at a local maximum.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by nsomaru on Wednesday May 29, 2019 @01:37AM (#20037106)
My default-config Streisand server was compromised according to Vultr. Just a heads up because VPNs can’t really afford this.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by NamTaf on Wednesday May 29, 2019 @02:34AM (#20037354)
Per the sibling comments, I'd definitely like to know more detail. I rely on Streisand when in China and so if it's something to do with Streisand itself then I want to be aware of that.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by stevekemp on Wednesday May 29, 2019 @02:20AM (#20037286)
Do you have further details? I mean this could be your server having SSH open and a weak root password, or it could be an exploit which hit Streisand, but we can't tell which ..
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by nsomaru on Wednesday May 29, 2019 @12:43PM (#20042372)
Replying to myself, I accepted what Vultr had to say and killed the server. Wasn’t really worth me investigating too deeply and I took them on their word.

I did the default Streisand install with all services, and disabled password based login on the box (keys only).

It seems Streisand has some issues updating some components according to their issues board and it seems like the maintainer might have abandoned it.

Next time I’ll probably use algo instead. I just need wireshark anyways ;)

Re:Wireguard-docs: Setup, usage, configuration, and a full e... by brianjking on Wednesday May 29, 2019 @01:46AM (#20037137)
Compromised due to Streisand being vulnerable or what?
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by Nursie on Wednesday May 29, 2019 @02:30AM (#20037336)
I managed to get StrongSwan IPSEC going in about an hour...

But then I'm looking for a configuration that allows me to route all my traffic via home from wherever I am, not a solution that allows me to route my home traffic via a third party.

Wireguard sounds interesting, and I'm going to learn more about it, but I like where I am with StrongSwan and just being able to issue a new certificate for a new device, and run with it.

Re:Wireguard-docs: Setup, usage, configuration, and a full e... by learntofly on Wednesday May 29, 2019 @06:51AM (#20038630)
I flagged the slow YouTube issues to iVPN (openvpn) previously but got palmed off by support, otherwise they offer an excellent service.
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by mingabunga on Wednesday May 29, 2019 @01:46AM (#20037139)
We've been working on a Windows version for the past few years, same idea - instant connection/disconnection, crazy fast, modern encryption. Uses only 10% of a single server cpu at gigabit speed. Almost finished, just adding in encryption for TCP (UDP and DNS already done). Shameless self promotion: https://www.firetrust.com/products/hideaway-secure-unlimited...
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by ubercow13 on Wednesday May 29, 2019 @01:49AM (#20037147)
Do you mean that your product is built on wireguard?
Re:Wireguard-docs: Setup, usage, configuration, and a full e... by mingabunga on Wednesday May 29, 2019 @01:55AM (#20037169)
No, it's not, it's our own implementation (except for the encryption part of course). We did a version similar to how Wireguard does it (UDP only) a few years back, but ran in to issues, so we ended up re-doing it with some different optimizations and UDP and TCP.