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

How to have freelance developers work on your server securely?

E

eggman2001

Guest
When I transfer files to my server, I always use SFTP so I'm minimizing the chances of someone else gaining ftp access to my server.

However, occasionally I have freelance developers work on my server (usually using a subdomain exclusively for development - i.e. dev.domain.com). When I send the developer the ftp login credentials, I do it via e-mail. I don't send them SFTP login info because they they could gain shell access and I don't want that.

Because I'm sending them the ftp login through e-mail, it's not secure. However, what would be the risks if this should fall into the wrong hands? Could someone upload a script that will attack my entire server? Or does plesk partition the directories in some way where they'd only be able to attack the folder that the malicious script gets placed in?

If what I'm doing is not secure, does anyone have any suggestions?
 
Back
Top