• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Is SSH access, via PuTTy, an encrypted connection?

Craig1986

Basic Pleskian
I recently needed to connect to my Plesk server, via SSH, using my Root credentials. My choice of software being PuTTy.

To achieve this, I had to perform the following commands, due to having previously disabled Root access via SSH:

Code:
login as: [Another user on the Plesk server]
password:  [user's password - hidden]

$ su - root
password - [root password - hidden]

The issue I then had was that I entered an incorrect root password. This then took me to the next line, where I entered the password again but it appeared on the screen in plain text as follows:

Code:
su: Authentication failure
$ [root password displayed]
-sh: 2: [partial display of root password]: not found

With the above in mind, I am wondering if the above Root password would had been sent over the network as plain text and thus become visible to attackers or would the password not be visible, due to the data transfer being encrypted, as I was already logged in as another user?
 
Hi Craig1986,

When you input the password after "Authentication failure", it was interpreted as a command; the command with a name like a password does not exist. The password (as all other text in SSH connection) encrypted before sending over the network.

But possibly the wrong password could be saved in the interpreter ("bash"? it depends on an interpreter) history file, e.g.: ".bash_history". Maybe this link could help you to check this: How to view the `.bash_history` file via command line?
 
Back
Top