9
Teosz
6y

Bought my first VPS, because the shared plan we are using is shit.

Spent just half an hour trying to log in, because upon registration they encouraged a strong password with simbols and everything.

But in reality a root password can only contain letters, numbers, underscore and minus sign... The fuck is wrong with you? Reducing the entropy is one thing, but really fucking up the most essential part of a VPN setup?

Comments
  • 4
    I don't know what kind of VPS you got but in a linux based system, this password:

    4Jeo1O8v8t1#!qwAHHqn7NF$PLvif

    Works perfectly.
  • 0
    @Merkury

    I know... I simply can't explain why they decided its a good idea. Going to try and change it, since i finally have access to it.
  • 2
    Every VPS service I've used gives you the opportunity to use key authentication. Can you not do that with your host? You can set a password on your private key. Sending passwords on the ether is scary, you're very brave.
  • 0
    @ymas
    Default is password, but I will do the key authentication once I'm home. For start I've changed the default port.
  • 0
    @ymas In any remote linux system you need to put the user's password at least once.
  • 1
    @Merkury hello there, if your public key is added to the authorized keys list on setup then there is no need for a password over the ether. For example, all my droplets on digital ocean are provisioned with a public key, never ssh'd with a password into any of my droplets.
  • 0
    @ymas well yes, if you can influence how a droplet is created, yes.

    But as a general rule when you get a VPS (not a drople, etc.) the provider don't put your keys there unless you ask them.
Add Comment