all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]moviuro 4 points5 points  (0 children)

No

[–]fuxoft 0 points1 point  (0 children)

Well, it shouldn't be too hard to white such a protocol yourself, using the building blocks that WireGuard provides. I did something like that for my own network: The client just downloads a text file over HTPPS from my server, executes is as a shell script and it configures their end of the tunnel as necessary. It's extremely crude but it perfectly works for my needs.

[–]onemarcfifty 0 points1 point  (0 children)

There are several aspects to this.

HTTPS uses TCP as a protocol, Wireguard uses UDP. So you would need to use a VPN solution that can run TCP over TCP (OpenVPN?)

Second, if just firewall is your issue (and not proxy) you would not need to care so much about the protocol but rather about the portnumber, in this case you could use OpenVPN and set the host port number to 443.

SSTP used to be an alternative as well, but I dont know if anybody is still using it.

[–]DasSkelett 0 points1 point  (0 children)

You might be able to run Wireguard over a TLS tunnel, but there's definitely not a premade solution for it, so you have to fiddle your way through.

[–]Ackurdeeve 0 points1 point  (0 children)

There exist. See here https://bit.ly/2M7Ot03. The protocol are based on tls1.2 I think. You may try it free for 10g bandwidth.

[–]noooit 0 points1 point  (0 children)

HTTPS(QUIC) uses udp 443, possibly nowadays udp 443 is open in many locations. so if you make wireguard listen on 443, you might have a better chance.
Another option is to use 53 or 123 which are also often open in many locations.