Search results

  1. F

    some hardening example for PVE on public IP

    Well, I just proposed a more secure approach. It is easier to filter traffic through a single server rather than doing it on every node. At least for the case when you have an infrastructure of a couple of nodes. Mostly I wanted to emphasize why running a privileged process on an unprivileged...
  2. F

    some hardening example for PVE on public IP

    You can use port knocking then. But a better approach is to use a VPS as an access point and even better in combination with a VPN. And access should be allowed only from the VPN or the VPS. At least that seems more reasonable the moment you start to develop an infrastructure.
  3. F

    some hardening example for PVE on public IP

    I am sure script-kiddies are different from one another with varying level of skills. Also, there aren't only script kiddies on the net. Why not to restrict access to SSH through the firewall? That would be a much better approach. Usually the best approach is to provide a system as vanilla as...
  4. F

    some hardening example for PVE on public IP

    Here is how security through obscurity goes down the drain: nmap -sV <hostname/ip> By the way, running SSH on an unprivileged port is a bad idea. When you run it on privileged port you know that it was started by root. Otherwise you are not sure who started it.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!