From: Roland Winkler <Roland.Winkler@physik.uni-erlangen.de>
To: help-gnu-emacs@gnu.org
Subject: Re: tramp and ssh-agent / ssh-add
Date: Sun, 30 Mar 2008 14:28:01 +0200 [thread overview]
Message-ID: <m363v4bdm6.fsf@tfkp07.physik.uni-erlangen.de> (raw)
In-Reply-To: mailman.9631.1206875452.18990.help-gnu-emacs@gnu.org
Michael Albinus <michael.albinus@gmx.de> writes:
> I wouldn't do it this way:
>
> - You advice tramp-open-connection-rsh, a function of Tramp 2.0. It
> doesn't exist anymore in Tramp 2.1, so you solution isn't future safe.
>
> - I believe that calling ssh-add on-the-fly is not the intended way. You
> should call it, before you run emacs "as a subprocess of ssh-agent" on
> the remote machine.
Of course I can run ssh-add before starting emacs. The reason I
didn't want to do that is that not all of these emacs sessions need
ssh at all. So I do not want to type a passphrase that is not needed.
That's why I said that if tramp had a (documented) hook that is
intended to be used for such kind of thing, I would definitely
prefer to use it.
> - Tramp supports password caching on its own. Install password.el in
> your own lisp directory. You could download it from <http://cvs.savannah.gnu.org/viewvc/*checkout*/tramp/contrib/password.el?revision=1.1.2.1&root=tramp&pathrev=branch-2-0-stable>.
From a security point of view this goes beyond my knowledge. I know
that I need to trust ssh that it handles the passphrases in a safe
way. (And I believe that ssh-agent /ssh-add does not cache the
passphrase itself, but it uses some other method.) When I have
another layer that is actually caching passwords, I feel
uncomfortable that one day something could go wrong. Or do I
misunderstand the approach used by password.el?
Roland
next prev parent reply other threads:[~2008-03-30 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 0:53 tramp and ssh-agent / ssh-add Roland Winkler
2008-03-30 11:12 ` Michael Albinus
[not found] ` <mailman.9631.1206875452.18990.help-gnu-emacs@gnu.org>
2008-03-30 12:28 ` Roland Winkler [this message]
2008-03-30 13:54 ` Michael Albinus
2008-03-30 14:25 ` Roland Winkler
2008-03-30 15:30 ` Michael Albinus
2008-03-30 15:38 ` Roland Winkler
2008-03-30 15:56 ` Michael Albinus
2008-04-01 0:17 ` Mike Mattie
[not found] ` <mailman.9640.1206887118.18990.help-gnu-emacs@gnu.org>
2008-03-31 7:44 ` Tim X
2008-03-31 10:26 ` Michael Albinus
[not found] ` <mailman.9696.1206959167.18990.help-gnu-emacs@gnu.org>
2008-03-31 21:04 ` Roland Winkler
2008-04-01 0:19 ` Mike Mattie
[not found] ` <mailman.9752.1207009209.18990.help-gnu-emacs@gnu.org>
2008-04-01 3:15 ` Roland Winkler
2008-04-05 4:38 ` Tim X
2008-04-07 4:32 ` Roland Winkler
2008-04-07 8:56 ` Peter Dyballa
-- strict thread matches above, loose matches on Subject: below --
2008-03-30 16:16 Roland Winkler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m363v4bdm6.fsf@tfkp07.physik.uni-erlangen.de \
--to=roland.winkler@physik.uni-erlangen.de \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.