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