• 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!
  • 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.

Issue Composer Not Found PHP

Actually, the most secure option is the chrooted shell. This jails the user to his own webspace. A webspace user should not be able to access anything outside of his own webspace. If you provide full access through another shell type, hackers will use this opportunity to install malware on your server. This will occur through unsecure or malicious plugins of the website software. Enabling full shell access can also lead to a total desaster as that user can then remove files and directories.
 
Ok, so I set up chroot, as I guessed, and then use the su command to log into root.
But at this point, couldn't hackers do the same?
 
When you login to a shell from within a subscription, your user account that logs in is the subscriber. When you chroot the environment, the subscriber is jailed to the subscription. The subscriber cannot escalate privileges to root.
 
Ok and here we are, but maybe you don't understand me?
I need to disable root, so first I need to create a user from which I can use the su command........
 
I suggest adding a new user using the Linux commands:
# adduser anotheruser

Next, set a password:
# passwd anotheruser

And add the new user to the wheel group that allows the user to su to root:
# usermod -aG wheel anotheruser

That should be enough to ssh to the server with the new user and become root.
 
Back
Top