• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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