…without snark or jumping down my throat. I genuinely want to know why it’s so unsafe.
I’m running a Synology DS920+, with my DSM login exposed through a Cloudflare tunnel. I have 2FA enabled, Synology firewall enabled with these rules in place. I also have this IP blocklist enabled.
After all of this, how would someone be able to break in via the DSM login?
VPNs are complicated enough that security experts are the only ones typically working on them… and they have a relatively small surface area with few 3rd party dependencies. So it’s about the best you could hope for. I agree there’s still a deep amount of trust. Your OS is generally a greater threat though… and your network gear probably a lesser one.
Where something like synology’s web admin involves a webserver running their software on a runtime (php? Python?) possibly with a database where the webserver, runtime, db drivers, db engine, orm, web framework, and all their third party modules are under continuous development and may not be patched. Plus they’re a targeted system because of their popularity. And they’re meant to be user friendly more than secure.
But having a Cloudflare reverse proxy helps a little. So would running something like fail2ban on the logs or a software level firewall configured to detect abnormal data.
Better would be to simply require a client certificate that you generate and distribute from an offline CA and have cloudflare do tls termination then whitelist only their IP(s) and your intranet IPs on the synology firewall.
Or… just use a VPN lol
I have setup a wireguard in server with dedicated ip. I followed the documentation and open few ports nothing else regarding security. I connect my home machine and my phone when needed to the wireguard serverso I can access jellyfin and other services.
Do I need to setup anything else, or is it already secure?
One more thing, is it recommended to connect my proxmox host to the wireguard VPN?
Sounds like you did a decent job. Why would you connect the Proxmox host to the VPN? Typically you’ll route certain local addresses (or whole subnets) via chain forwarding. That way, when you connect to the VPN it’s as if you’re on the local network. The way you’re describing it, you would need to know it’s VPN IP which is usually dynamic. And you don’t typically want VPN clients to be able to access each other - just the local network. It really all depends how you set everything up.