|
| ▲ | 8fingerlouie 2 hours ago | parent | next [-] |
| Compared to faffing around with certificates, Wireguard or if you're lazy, Tailscale, is a breeze to setup. Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance. Tailscale is easier (presumably), but also puts a corporate entity between you and your data. |
| |
| ▲ | devilbunny an hour ago | parent [-] | | Tailscale is ridiculously easy, and headscale is a thing. It doesn't support everything corporate Tailscale does, but it covers the basics of "get me into my network from anywhere". You can run it on a $1/month VPS that has a public IPv4 address. I don't work with computers professionally, at all. It still only took me about 2 hours to get the VPS, get Debian going on it, set up headscale, and connect to it from home. Do I still use corporate Tailscale? Yes, it has some features that aren't beautifully supported on headscale, and so for the moment I'm fine with that. But I do have my backup plan in place if I need it. | | |
| ▲ | rlt 32 minutes ago | parent [-] | | Personally I’d rather let Tailscale manage securing the public-facing service than use Headscale. Tailnet Lock seems like a good compromise. And as much as I’d like to use it, I don’t trust Tailscale SSH. | | |
| ▲ | devilbunny 14 minutes ago | parent [-] | | I agree, but if people want no corporate dependency at all, it's there. I have a headscale instance, on one of those $1/mo VPSes, and I don't intend to use it unless I have to. But if I have to, it's there. |
|
|
|
|
| ▲ | cloudfudge an hour ago | parent | prev | next [-] |
| How many mTLS configs are anything but all-or-nothing access? It is so common for an app to slap mTLS on the endpoints and make the rule "anyone with a valid cert is admin on this API; anyone else gets 401." This is a step back towards a superuser/regular-user model. Now if you're going to use mTLS as the basis for mature authn/authz, that's a different story. But I never see anyone do that. |
| |
| ▲ | landgenoot 29 minutes ago | parent [-] | | Applications are vulnerable for exploits. mTLS prevents connecting to the application without valid cert. Sure the reverse proxy handling the mtls can be exploited, but so can any VPN server as well. |
|
|
| ▲ | Liuser 2 hours ago | parent | prev | next [-] |
| VPNs these days are far easier to configure than mTLS (which often need proxies on both server and client side to handle the TLS terminations and needing to worry more with certificate lifecycle). mTLS is a better option for distributed systems (service to service mesh networks for attestation of workload identities) instead of for human users. |
|
| ▲ | para_parolu 2 hours ago | parent | prev | next [-] |
| How are they bad? You turn it on and it works. Don’t need to touch it. Don’t need to deal with anything but pasting key or scanning qr code |
| |
| ▲ | landgenoot an hour ago | parent | next [-] | | I want to make sure every picture I take will be backed up to the NAS. Do I turn on the VPN when I take a picture and turn it off when finished? Every time? What if I need multiple VPN's? Living in a country that has a bad geoip reputation, it's already a struggle of switching on and off for individual websites to work. | | |
| ▲ | akerl_ 3 minutes ago | parent | next [-] | | How do I set up mTLS for my phone's camera roll? | |
| ▲ | Gigachad an hour ago | parent | prev | next [-] | | You set up Tailscale as a split tunnel so requests to your own server go through the vpn while everything else does not. | |
| ▲ | xeetzer an hour ago | parent | prev [-] | | You can do split tunneling and only forward certain ips (or apps) through the vpn for your first problem. | | |
| |
| ▲ | katbyte an hour ago | parent | prev [-] | | How does a rando tv connect to something behind a vpn like Emby or jf? | | |
| ▲ | Gigachad 44 minutes ago | parent [-] | | Your TV is probably on your home network. If not you could use one of those cheap travel routers to connect the hotel tv to your local |
|
|
|
| ▲ | gmerc 2 hours ago | parent | prev | next [-] |
| tailscale / wireguard on your router are completely transparent |
| |
| ▲ | bigwheels 2 hours ago | parent [-] | | Strongly agree, Tailscale / WG is the way go. Unless something needs to be available to randos on the Internet, in which case mTLS is still a huge headache. |
|
|
| ▲ | LoganDark 2 hours ago | parent | prev [-] |
| mTLS is the one that requires a client certificate. right? It can be quite difficult to get protocols other than HTTPS to behave well with that, mostly because the application has to worry about it and many don't bother. |
| |
| ▲ | landgenoot 2 hours ago | parent [-] | | Yes, that's correct. It's like SSH private keys, but for HTTP | | |
| ▲ | QuantumNomad_ an hour ago | parent | next [-] | | WireGuard is also very much like SSH private keys. A basic config to set up a VPN that only adds access to services on the VPN itself is very short and simple, both for WireGuard server and for WireGuard clients. You can run the WireGuard server from your home computer. For example on your NAS machine itself or some other machine you have at home. And open the port for WireGuard to the outside. Also some routers can run WireGuard server on the router. For example Mikrotik routers have WireGuard server built in and ready to configure [0]. Routers running OpenWrt can too [1]. Or you can rent a small VPS and use that as your WireGuard server. And then, any which where you run the WireGuard server, run the WireGuard client on your laptops, iOS and Android devices, and connect client apps using VPN internal IP addresses. And your NAS etc too, if the WireGuard server isn’t running on the NAS machine itself. It really is quite quick to set up with server and all clients across devices. The only real hurdle is that on iOS you have to turn the VPN back on manually after reboot and which is sometimes easily forgotten if you only use your self hosted services occasionally. But you quickly realize oh right I have to open the WireGuard app and turn on the VPN again whenever you try to use one of your self hosted services and the client isn’t connecting. [0]: https://manual.mikrotik.com/docs/virtual-private-networks/wi... [1]: https://openwrt.org/docs/guide-user/services/vpn/wireguard/b... | |
| ▲ | LoganDark 2 hours ago | parent | prev [-] | | I think if you want mTLS to have any significance, the application itself has to support it, otherwise you're just doing a VPN again and there's no good reason to use it over Wireguard (especially because an mTLS server will respond to port scans and a Wireguard server will not) |
|
|