Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 1
    I don't have the root password, and I'm not sure I feel comfortable putting my key in there without permission from the people who own the server. The true shortcut that it's doing for me is saving me from ssh-ing, sudo cp-ing, scp-ing, editing, scp-ing, ssh-ing, sudo cp-ing (as my user cannot read the file). sshfs may be the way to go here Commented Jun 27, 2016 at 19:02
  • There's a good chance that sshfs won't work either if you don't have ssh access to root. The remote file system would likely be mounted with only your permissions. I think at this point, your only option is ssh remotesystem sudo vim file Commented Jun 27, 2016 at 19:07
  • You're right - sshfs doesn't work (and you pointed out to me that I had accidentally chowned a bunch of files to myself that shouldn't have been...) though I thought it was working Commented Jun 27, 2016 at 19:14
  • 1
    @Mitch - The people who own the server gave you an user account, and, i believe, you're accountable for what you use that account for. You're placing there a public key which anyone with access to that account could. You're tying the permissions of that account to the possession of the private key just as much as the knowledge of the password allows. i.e. form the server's point of view there is no difference between having a key or knowing the password. Commented Jun 27, 2016 at 20:20
  • Bottom line: I think you're right to hesitate to put your public key on that server. I think you're stuck with ssh/sudo vim Commented Jun 27, 2016 at 20:45