top 18 comments

sorted by: hot top controversial new old
[–] 22 points 8 months ago (6 children)

Enabling SSH password authentication is unnecessary and not a good idea, especially if your temporary passwords are simple. I haven't used Hetzner but there is probably a way to upload a file or to paste into the console, or else if you fix your keyboard you could at least type a URL to download the public key from the internet. You may want to look into cloud-init instead of manually installing and configuring your VMs.

LUKS may not make your server meaningfully more secure. Anyone who can snapshot your server while it's running or modify your unencrypted kernel or initrd files before you next unlock the server will be able to access your files.

  • source
  • hideshow 6 child comments
  • [–] 10 points 8 months ago (3 children)

    Why full disk encryption is important: what happens when you switch servers or providers: can you be sure the disk gets wiped properly?

    Or when your disk dies and gets replaced, what happens to the old disk? Will they physically destroy it or just throw it in the bin?

    When encrypted, it doesn't matter; no one will get data off of them. That's why you encrypt servers.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 5 points 8 months ago (2 children)

    It's worth going through the provider's policies.

    For example, here's how Hetzner handles deletion of your data

    Encryption will prevent mistakes, but if you can't trust the provider's policies you shouldn't trust them to run your infrastructure at all.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 8 months ago (1 child)

    Security is always applied in layers. The more the better. There's a reason "encryption at rest" is a requirement in many audits.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 8 months ago

    Agreed. I was going to argue more against encryption, but you can see me somewhat changing my mind in the second half of my comment.

    For me personally, I don't want the hassle of encryption on my VPS and have decided I'm fine with the remaining risk.

  • source
  • parent
  • [–] 1 point 8 months ago

    LUKS may not make your server meaningfully more secure. Anyone who can snapshot your server while it's running or modify your unencrypted kernel or initrd files before you next unlock the server will be able to access your files.

    This is a little oversimplified. Hardware vendors have done a lot of work in the last 10-20 years to make it hard to impossible to obtain data this way. AMD-SEV for example.

    There are other more realistic attacks like simply etrackt the ssh server signature and MITM the ssh connection and extract the LUKS password.

  • source
  • parent
  • load more comments (1 reply)
    [–] 7 points 8 months ago (1 child)

    Still better than nothing.
    But there is also a possibility to dump the RAM and recover a key or data.

    If you can, store only pre-encrypted data.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 2 points 8 months ago

    I've had a similar issue with / and some special keys. Numpad solved the / problem, using the system through SSH allows properly using your keyboard, and I'd imagine keybinds such as Gaomon's or AntimicroX's could be used too.

  • source
  • [–] [B] 4 points 8 months ago* (last edited 8 months ago)

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

    Fewer Letters More Letters
    DHCP Dynamic Host Configuration Protocol, automates assignment of IPs when connecting to a network
    IP Internet Protocol
    SSH Secure Shell for remote terminal access
    VPN Virtual Private Network
    VPS Virtual Private Server (opposed to shared hosting)

    5 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

    [Thread #151 for this comm, first seen 9th Mar 2026, 14:00] [FAQ] [Full list] [Contact] [Source code]

  • source
  • [–] 3 points 8 months ago

    Why not cloudinit instead of ssh?

  • source
  • [–] 2 points 8 months ago (7 children)

    Am I the only one using a random 5 digit port for ssh? Why using the default port 22? It's just saving time for an attacker.

  • source
  • hideshow 7 child comments
  • [–] 9 points 8 months ago

    To me, the nonstandard port is mostly nice for reducing log spam from scripts. The risk is that using a nonstandard port lulls one into a false sense of security and overlook good sshd practices. Good sshd practices will prevent the script-kiddies just as well as the non-standard port, while a non-standard port will not challenge a targeted attack. And, if you interact with multiple servers, it can be inconvenient to remember a different port for each one.

  • source
  • parent
  • [–] 5 points 8 months ago

    I use nonstandard ports for just about everything such as Docker containers, including ssh. However, modern bots are quite capable of scanning your server for vulnerabilities, CVE, zero day, and SSH. A non standard SSH port does reduce noise a bit but isn't a reliable defense against scanners.

  • source
  • parent
  • [–] 2 points 8 months ago (4 children)

    The whole port range can be scanned in under a second. A real attack does not care if your ssh port is 22 or 69420. Changing Port is just snake oil.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 8 months ago (2 children)

    It can be scanned, but definitely not under a second.

  • source
  • parent
  • hideshow 2 child comments