You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And immediately be tramp root on the remote server. Sudo is more useful than su in this case because not everyone has the root password on a remote server, but many people do have sudo -i access to root.
Additionally if we put in ~/.authinfo or ~/.authinfo.gpg sudo password credentials for the remote server,
machine serv1 login root port sudo password MYSUDOPASSWORD
and if in ~/.ssh/config we have something like,
Host serv1
HostName serv1.example.com
User MYUSERNAME
We can securely tramp as root on remote servers via sudo not needing a password or anything. It can be quite handy. I'd love to have this with a shell-mode shortcut similar to :ssh
In like manner,
:su would be nice for quickly becoming tramp root on your local machine, with e.g. something similar to,
(cd (concat"/su:" (system-name) ":"))
(shell)
and this would not require root's password again, if stored as follows in ~/.authinfo.gpg
machine HOSTNAME login root password MYPASSWORD
The text was updated successfully, but these errors were encountered:
for example, I can type:
And immediately be tramp root on the remote server. Sudo is more useful than su in this case because not everyone has the root password on a remote server, but many people do have
sudo -i
access to root.Additionally if we put in ~/.authinfo or ~/.authinfo.gpg sudo password credentials for the remote server,
and if in ~/.ssh/config we have something like,
We can securely tramp as root on remote servers via sudo not needing a password or anything. It can be quite handy. I'd love to have this with a shell-mode shortcut similar to
:ssh
In like manner,
:su would be nice for quickly becoming tramp root on your local machine, with e.g. something similar to,
and this would not require root's password again, if stored as follows in ~/.authinfo.gpg
The text was updated successfully, but these errors were encountered: