Facebook
Twitter
-
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
CentOS2Alma discussion
Question .ssh directory in domain folder?
- Thread starter uniauto
- Start date
Yes, that is correct when you allow SSH access for the subscriber.
Hi, thank for answer.
I'm running Plesk Web Admin Edition and didn't change anything about SSH since.... can't remember.
Domain/ftp users have SSH access forbidden since forever.
Maybe .ssh folders and keys was added by any extension? NodeJs, Git, Laravel and Composer was autoinstalled yesterday.
The same here. That directory has appeared on my 3 servers. It has also auto self-installed Git, NodeJs, Laravel and Phusion Passenger server. SSH is forbidden since forever on all subscriptions
This is not something new. I've seen these folders inside subscriptions, too. The .ssh folders were created a year ago.
Have you installed the SSH Terminal extension? That's the only extension with a link to those directories that comes to mind. Or maybe the Git extension?
Maybe one of the developers can clarify this?
Have you installed the SSH Terminal extension? That's the only extension with a link to those directories that comes to mind. Or maybe the Git extension?
Maybe one of the developers can clarify this?
You can uninstall the Laravel Toolkit just like any other extension:
To prevent extensions from installing, you can add this in the panel.ini extension:
Add additional extensions that you don't need or want to be installed.
Use this command to find the correct name of the extension:
To prevent extensions from installing, you can add this in the panel.ini extension:
Code:
[extensions]
blacklist = sectigo,ssh-terminal,git,laravel,nodejsAdd additional extensions that you don't need or want to be installed.
Use this command to find the correct name of the extension:
Code:
# plesk bin extension -l
...Thanks!
I still don't know why those .ssh folders were created, so I'm not sure if something depends on it.
@Peter Debik or @AYamshanov, do you know where these .ssh folders come from?
For access it wouldn't need id_rsa*, though. Only authorized_keys, if at all.
I think it at least could come from the Git extension, here is an quick example (please ignore the fact of the error, it is just to show the process/steps),
When you add a repository for the first time, the extension generates ssh-pair, private and public keys,
I have tried to add git-repository through a link to git (
[email protected]:plesk/ext-advisor-integration-example) and the first step is adding its public key into the list of known hosts inside the .ssh directory,
Finally, in the
.ssh directory I can see 3 files,git_known_hosts, it contains a public key for git repository,id_rsa, it contains a private key for the Git extension on that domain,id_rsa.pub, it contains a public key for the Git extension on that domain.
