ChatGPT解决这个技术问题 Extra ChatGPT

Open file via SSH and Sudo with Emacs

I want to open a file inside Emacs which is located on a remote server, with sudo powers on the server. I can open local files with sudo via Tramp like this:

C-x C-f /sudo::/home/user/file

But I want to use sudo on the server:

C-x C-f /sudo::user@server/home/user/file

But this gives me sudo powers on my local machine, it asks for my sudo password on the local machine. Is there a way to use sudo on the server?

BTW: Emacs is not installed on the server

can't you command as root directly on the server?
I have a user with sudo privileges, but not the root password.

p
phils

As of Emacs 24.3, an analog of the old multi: syntax has been layered on top of the modern tramp-default-proxies-alist approach, meaning that you can once again perform multi-hops without any prior configuration. For details, see:

C-hig (tramp)Ad-hoc multi-hops RET

With the new syntax, each 'hop' is separated by |. The example in the manual is:

C-xC-f /ssh:bird@bastion|ssh:you@remotehost:/path RET

Which connects firstly as bird@bastion, and from there to you@remotehost:/path

/su: or /sudo: on remote hosts

You can also use this syntax to sudo/su to root (or of course any other user) on a remote host:

C-xC-f /ssh:you@remotehost|sudo:remotehost:/path/to/file RET

Important: be sure to specify the hostname explicitly: sudo:remotehost: rather than sudo:: (see below).

As this still uses the proxy mechanism underneath, tramp-default-proxies-alist should now include the value ("remotehost" "root" "/ssh:you@remotehost:")

Meaning that the proxy /ssh:you@remotehost: is going to be used whenever you request a file as root@remotehost.

root is the default user for these methods, but you can of course also change to a non-root user with:

C-xC-f /ssh:you@remotehost|sudo:them@remotehost:/path/to/file RET

Always specify the remote hostname explicitly

You are probably used to using sudo:: or su:: and omitting the hostname. If you are staying on the localhost then this is still fine, but if you are hopping to a remote server then you must specify the hostname for every hop -- even if it is the same as for the previous hop. Always use sudo:hostname: or su:hostname: with remote hosts.

The trap here is that sudo:: does actually appear to work -- however when you do that the HOST for the dynamic proxy entry will be the hostname you originated from rather than the host you connected to. This will not only look confusing (as the wrong host will be displayed in the file paths), but it will also mean that any subsequent attempt to use sudo:: on your localhost will instead be proxied to the remote server! (and the proxy would also presumably be clobbered if you did the same thing on a second server, causing further issues).

In short, don't use :: when you multi-hop!

Emacs 27+

Starting from Emacs 27.1 (or Tramp 2.4.2, if using the GNU ELPA package) the :: case works intuitively, such that /ssh:you@remotehost|sudo:: will re-use remotehost rather than your own local host, and so you won't end up with a bad proxy entry.

In addition, the likes of /ssh:you@remotehost|sudo:localhost: are detected and flagged as user errors.

If you are liable to use a mixture of Emacs versions including versions earlier than 27 (or you are advising someone else who may be using an older version), then it would be safest to continue to treat :: as unsafe when multi-hopping, to avoid potential mishap. (I.e. specifying the correct remote host explicitly will remain the safest approach if the Tramp version is unknown.)


and now added to wikemacs as well wikemacs.org/index.php/TRAMP. Thanks phils, it works great.
I just found this answer, and it works great...except that I have hostname shorthand defined in an .ssh/config file. When I type /sudo:hostname:/etc/hosts, I get what you would expect, but when I type /sudo:abbrev:/etc/hosts, I get the message "Host abbrev looks like a remote host, sudo can only use the local host". Is this fixable?
rogerl: I also have .ssh/config entries, and I don't have any problems using /ssh:abbrev|sudo:abbrev:/etc/hosts for my hostname abbreviations. It looks like you're not hopping to the host first.
@phils Perhaps I should post this as a new question. However: my config file looks like Host r User rlipsett Hostname odlinux IdentityFile ~/.ssh/id-rsa.pub and my tramp-default-proxies-alist appears to be correct. Yet the behavior I described above persists. Is my config file somehow wrong?
Quick update -- As of Emacs 27, the :: case will work the way you want it to, such that /ssh:you@remotehost|sudo:: will re-use remotehost rather than your own local hostname, so you won't end up with a bad proxy entry. In addition, the likes of /ssh:you@remotehost|sudo:localhost: are detected and flagged as user errors. (Of course, if you are liable to use a mixture of Emacs versions, you should continue to treat :: as unsafe when multi-hopping in general, to avoid potential mishap.)
C
Community

Update: Although this answer solved the original problem, it was written for emacs 20 or 21. For emacs 24, I recommend you use phils's answer because it offers more explanation and is up to date.

I think multi-hop filenames in tramp is what you're looking for.

The first hop would be ssh and the second would be sudo.

Update: Recent versions of emacs support multiple hops using proxies:

(add-to-list 'tramp-default-proxies-alist ("my-sudo-alias" nil "/ssh:user@ssh-host"))

Then invoke by opening:

/sudo:my-sudo-alias:file-on-ssh-host

This seems like the solution, but I get: "multi method is no longer supported" Can you point me to an updated manual?
M-x info, C-s tramp :) You may need to define a fake host as the target of your sudo and add it to tramp-default-proxy-alist.
I couldn't get it running in my configuration (error 255?), but the following line in .emacs works: (set-default 'tramp-default-proxies-alist (quote (("my-sudo-alias" nil "/ssh:user@ssh-host:"))))
The updated answer doesn't define "recent", has invalid elisp, and doesn't work even when you correct it. I'm on a stable version of emacs released over a year after the updated answer.
The real answer as of 2014/24.3 is the following answer, using "ad-hoc multi-hops"
n
npostavs

I had some troubles with the selected answer. However, it worked when I added this line to .emacs:

(add-to-list 'tramp-default-proxies-alist '(".*" "\\`root\\'" "/ssh:%h:"))

And then executed the following:

/sudo:ssh-host:file-on-ssh-host

It was slightly confusing because at one point I was prompted for the "root" password, but entering my user's password granted me access. It also universally works on all hosts on the network. Also, I can still do this to not be root:

/ssh:ssh-host:file-on-ssh-host


This was not working for me. It looks that in Ubuntu, at least with version 23.2.1 of Emacs and version 2.1.18-23.2 of tramp this does not work. This works, though: info.solomonson.com/content/…
(set-default 'tramp-default-proxies-alist (quote ((".*" "\`root\\'" "/ssh:%h:"))))
I am not able to get either of the solutions above to work (add-to-list or set-default). The first causes Emacs to choke on startup and the second gives me "Host abc.xyz.com' looks like a remote host, sudo' can only use the local host" as soon as I enter the second colon in "/sudo:abc.xyz.com:". Ideas? Emacs 23.1.1 on Ubuntu 10.04 LTS.
v
vampolo

From the tramp multi-hops configuration webpage

 (add-to-list 'tramp-default-proxies-alist
                   '(nil "\\`root\\'" "/ssh:%h:"))
      (add-to-list 'tramp-default-proxies-alist
                   '((regexp-quote (system-name)) nil nil))

Then any

C-x C-f /sudo:remote-host:/file

will open file using sudo after logged with the same username of the user running emacs but on the remote machine.


D
Dan Andreatta

You have to ssh into the server first, then you have to run emacs locally.

Or you can use NFS with no_root_squash, or you can try with emacs server/client, although I have no idea of what may happen (do not use emacs myself)


I tried, but I cannot access files as root with sshfs, when mounting it as regular user. I guess it is a setup problem.
As Hassan noted, no_root_squash should be used with care.
-1 for not answering the question. -1 for suggesting NFS instead of SSH. -1 for suggesting no_root_squash. -1 for suggesting Emacs client, which uses usually Unix domain sockets, for a remote communication problem. -1 for blethering about Emacs without using it.