|Subject:||Re: Using a 'bastion' - issue when providing password|
|Date:||Mon, 06 Oct 2014 23:50:17 +0200|
I think Michael meant that you create an additional ~/.ssh/config entry beyond the "bel" one that you've got already.
If I recall correctly, you had to do
ssh -t bel address@hidden, and
bel was an entry in
So: create a new entry "rt" in
~/.ssh/config that does
ssh -t bel address@hidden behind the scenes :-)
How to do that? Hmmm.
Host rt ProxyCommand ssh -t bel address@hidden
Maybe that works, I'm not sure.
On 3 Oct 2014, at 15:50, SENESI Stéphane wrote:
Thanks for taking time for user support during your vacation !!
Three remarks :
----- Mail original -----
| De: "Michael Albinus" address@hidden
| À: "SENESI Stéphane" address@hidden
| Cc: address@hidden
| Envoyé: Vendredi 3 Octobre 2014 13:39:20
| Objet: Re: Using a 'bastion' - issue when providing password
| Hi Stéphane,
| I am on vacations just now (btw, in France :-)
Enjoy ! but mind that weather will become rainy from Sunday for most parts of France
| so I cannot check in detail until I return. For the time being you might try
| to add an entry to ~/.ssh/config for your bastion host, which fires the
| needed command.
As far as I understand, these bastion won't accept the user to isseu command, either directly or not, but only react to one of the two options I quoted (providing address@hidden on first ssh command, or choosing an entry in a address@hidden's list
| Furthermore, there is a variable tramp-password-end-of-line (or so), maybe
| you could tweak it somehow.
Do you refer to :
proc (concat (tramp-read-passwd proc) tramp-local-end-of-line))
If yes, my value for tramp-local-end-of-line is C-j, which seems sensible .... If not, where is the best place to change it ?
| Best regards, Michael.
----- Météo-France -----
Fixe : +33 561079931
Tramp-devel mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|