Skip to main content

Whole server access recommendations for web developer

Comments

2 comments

  • rhenderson
    We use CoreFTP for SSH/SFTP using a custom SSH port, then you could turn off FTP but you still have to login as each user to keep your permissions straight. This would at least help with your brute force attempts. You can login as root this way (if your SSH configuration allows it) but if you edited different users files the ownership would be wrong/reset as root. You might be able to use expandrive and setup multiple local folders to sync with and have expandrive login to each account as the account owner, then when you change the files locally they would propagate properly to the server with the correct ownership. I played around with doing something similar in the past and it worked pretty much like you are wanting, it's only $40; we just did not use it enough to buy the software. We have not tried the newest version - They do have a mac version
    0
  • cPanelMichael
    Hello :) Have you considered using SSH as "root"? You could then "su" to individual account usernames when making changes to files owned by those accounts. Otherwise, SFTP might be a better option if you want to use a client such as FileZilla to login as the account username and upload files. Thank you.
    0

Please sign in to leave a comment.