• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

sFTP/SCP

S

swardell

Guest
Is it currently possible to config 8.1 (for Linux) to use sFTP or SCP and when will be it a standard feature?
 
By SFTP I assume you mean FTP over SSH?

If so it works now, here's how.

Turn on for your domain user:
/bin/bash (chrooted)

Now your domain admin can connect via SFTP.

You then can go further and block port 21 on the firewall, therefore forcing them to use SFTP.

Cheers,

David
 
but that requires enabling and allowing the users shell access which I dont want to do, any other way?

and, of course, an fully integrated method in the panel would be nice
 
Nope :(

But what is the difference? the ftp user id / password they can delete a hell of a lot of stuff. Also the shell its chrooted anyway.
 
There's definitely a difference. Chrooted shells can be broken through various exploits, scp is a better option IMHO.

We've installed SCPOnly, works well. We just manually added the SCPOnly option to one of the tables in the PSA database to get it to show up in the Plesk interface.

http://sublimation.org/scponly

~Matt
 
Sftp-server

You can add:

/usr/libexec/openssh/sftp-server


To /etc/shells

And then select this in the account as their shell. This will give them access to only sftp with not additional software required.
 
Originally posted by matt.simpson
There's definitely a difference. Chrooted shells can be broken through various exploits, scp is a better option IMHO.

We've installed SCPOnly, works well. We just manually added the SCPOnly option to one of the tables in the PSA database to get it to show up in the Plesk interface.

http://sublimation.org/scponly

~Matt
Hello Matt,

could you please elaborate on this some more?

"We just manually added the SCPOnly option to one of the tables in the PSA database"

Which table do you mean and how did you do this? I'd also like to make file transfers to our server a bit more secure than with plain FTP (which is really insecure). I would like to get SCP working, but need to know a bit more. Hope you can help and TIA.

Scott
 
Re: Sftp-server

Originally posted by huck
You can add:

/usr/libexec/openssh/sftp-server


To /etc/shells

And then select this in the account as their shell. This will give them access to only sftp with not additional software required.

So huck if I simply edit /etc/shells and add /usr/libexec/openssh/sftp-server

And select that for the users shell access thats all?

Cheers,
David
 
Re: Sftp-server

Originally posted by huck
You can add:

/usr/libexec/openssh/sftp-server


To /etc/shells

And then select this in the account as their shell. This will give them access to only sftp with not additional software required.

WARNING

This works, BUT the user is not chrooted, so they can traverse the entire filesystem!
 
Back
Top