Nothing gets through the firewall anymore. So now my only vulnerability (I hope) is the firewall, OPNsense.
I've been using Synology for ~12 years, and I've never exposed my NAS to the Internet.
Unfortunately, Synology apps don't support it.
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, either 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...
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.
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.
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.
You trust yourself with a VPS and correctly configuring a beast such a Debian?
I don't mean to be harsh but even as a professional developer I'm frequently humbled by our grumpy sysadmins on (to me) arcane stuff I didn't knew existed.
They are prime targets and have large attack surface. Even bigger companies are frequently compromised. It's a matter of time before it becomes publicly known.
mTLS is a better option for distributed systems (service to service mesh networks for attestation of workload identities) instead of for human users.
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.
https://github.com/alangrainger/immich-public-proxy/blob/mai...
I have one on-demand VPN with a list of internal IPs to route.
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.
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.
If I told you not to use a power drill as a hammer, you wouldn't claim I'm saying the hammer is at fault for being a bad power drill.
I just take issue (maybe pedantically so) calling it a bad tool and blanket statements that no one uses it for just authn but for authz also. It’s not used for authz. The absence of authz shouldn’t be blamed on mTLS.
Let the family members have their own Linux ISO collections or let them pay streaming scammers.
I am not a big family guy as you can notice. But in my defense no one really cares about my photo albums or ISO files I like.
I personally think Synology are mostly at most fault here though - they shouldn’t be making it so easy for clueless users to do this. It’s basically advertised as a feature.
Very, very few consumer products make it that easy to set up and tie your own noose.
Synology was a perfect solution. Low-cost unit, stick a 15gb drive in it and do again for second unit. DSM is a breeze to work with and the built in rsync was pretty easy to setup and has been working seamlessly for a year now.
Just free willy opening ports and sticking a default setup NAS to the internet, I agree, is asking to be hacked. Tailscale was my preferred way to get them connected but there is no Tailscale Synology client, and if I remember, would required hacks to get one on it and working. Use long passwords for the user is first start. Then on both use the security settings to only accept the ONE IP from each other, even though only one of them is actually exposed to the internet. Also select the settings to install any security updates automatically. Logs show this has all been working good to protect the units. The only catch so far is the IP of his house changed once in the year, being it isn't static, but simply changing it on the sending unit to new one fixed it in about 3 minutes.
I'm thinking of replicating this setup for myself to backup all PC's and phones in my household and syncing to another unit I set up at my relative's house in another state while I visit over the holidays. It pays for itself in short time compared to a cloud provider.
I'm curious now after this CVE how long it will take the units to auto update to newest version after it becomes available to manually install.
The thing even self-updates.
Anyway, I bought one for a client past year, and I won't buy nor recommend one ever again. It's a mess security and technically wise.
They're on a 4.4 kernel (even on recent devices), supposedly backporting security bugfixes. That also means that on a kernel so old you don't have the networking performance improvements and features of the last 10 years.
They're using a btrfs version they forked 10 years ago that they're maintaining out of tree, that also doesn't have any of the new features, and that's not compatible with recent btrfs versions. On top of that, they self built a super messy ACL system that's using a vmtouch version also from 10 years ago.
They always have super outdated libraries. They've been using PHP7.4 (EOLed 4 years ago) until past winter, and PHP8.1 until this summer.
I take a look to the running daemons and... their SMB daemon is based on 4.15.13 (from 2022). Nginx 1.23.1 (from 2022). chrony (it just says DEVELOPMENT version). net-snmp 5.9.3 (2022). rsync 3.1.2 (2015). Postgres 11.11 (2021). Not fun.
And I'm talking about a supported device that got a major OS upgrade this summer.
With this wave of AI security attacks, they don't have much time until something huge appears. Either that, or they use that AI to accelerate going back to mainline versions of the software they use.
--
0: https://tailscale.com/docs/integrations/synologySynology isn't a panacea (they put themselves in an awkward position with their btrfs fork, with constraints them to stay on an obsolete kernel branch and do a ton of patch shuffling and backporting), but is a much better posture to start homelabing from than, say, a raspbian in a shoebox.