From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: tramp sudo or not sudo on remote server
Date: Mon, 29 Aug 2011 10:20:02 +0800 [thread overview]
Message-ID: <87ipph9cx9.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 8762lha0gy.fsf@gmx.de
On Mon, Aug 29 2011, Michael Albinus wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> Hi,
>
>> The tramp manual explains how to access files as root on a remote
>> server, with a two-jump system, but there doesn't seem to be any way to
>> do this selectively: if I define a proxy, it seems to have me as root
>> for all files on that server.
>>
>> Is there anyway to define two different methods for the same server, one
>> that operates as my normal user and one that does a second jump to work
>> as root?
>
> There is no need to apply sudo for a normal user, you could always
> access via ssh like "/ssh:user@host:". This does not interfere with your
> proxy settings for root.
Sorry, I think I confused myself by using .ssh/config to define
Host shortcuts for servers, such that "/bl:/path" goes to a certain host as a
certain user. Presumably I wouldn't be able to use this trick if I want
to use switch between my regular user and sudo. There are a couple of
awfully long host names, though -- are there any other shortcuts I can
use?
I tried defining another Host block ("sbl") in .ssh/config, where only the
hostname and not the user were specified, but /sudo:sbl:/path just told
me that sbl was a remote host and sudo couldn't be used for remote
hosts…
Thanks again, this at least got it working!
Eric
next prev parent reply other threads:[~2011-08-29 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 10:37 tramp sudo or not sudo on remote server Eric Abrahamsen
2011-08-28 17:51 ` Michael Albinus
2011-08-29 2:20 ` Eric Abrahamsen [this message]
2011-08-29 18:52 ` Michael Albinus
2011-08-30 2:36 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ipph9cx9.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).