Kai.Grossjohann@... (Kai Großjohann) writes:
> Marco Lonsing <Marco.Lonsing@...> writes:
>
>> Kai.Grossjohann@... (Kai Großjohann) writes:
>>
>>> Marco Lonsing <Marco.Lonsing@...> writes:
>>>
>>>> 1.) Shouldn't the ssh method allow interactive logins? That doesn't
>>>> work. Tramp is waiting at the password prompt until it times out.
>>>
>>> It should indeed. Thanks for testing. The mechanism for finding
>>> password prompts has changed. So maybe I b0rked a regexp. Can you
>>> try again, until the *tramp/foo* buffer contains the password prompt,
>>> then send me that buffer?
>>>
>>> Ah, I think I found it. Please try the patch after my signature, or
>>> the most recent version from CVS.
>>>
>> OK password prompt and prompting for unknown hosts is working now. But
>> if ssh gets an invalid fingerprint tramp simply stops. IMHO tramp should
>> raise the buffer with the corresponding output.
>
> I recently changed Tramp to grok the following question:
>
> Are you sure you want to continue connecting (yes/no)?
>
> If you mean another question, please show me some output so I can add
> a regular expression for this. If the above is the question you
> mean, please try the current CVS to see if it works.
>
No there is no question I meant the situation when an admin has
installed new host keys. In this case ssh stops with the following
output:
Warning: Server lies about size of server host key: actual size is 1023 bits vs. announced 1024.
Warning: This may be due to an old implementation of ssh.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA1 host key for aix has changed,
and the key for the according IP address 134.147.215.35
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/marco/.ssh/known_hosts:3
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA1 host key has just been changed.
The fingerprint for the RSA1 key sent by the remote host is
c9:5c:6f:69:0d:65:c9:97:dd:9f:f7:ca:f7:82:f7:58.
Please contact your system administrator.
Add correct host key in /home/marco/.ssh/known_hosts to get rid of this message.
Offending key in /home/marco/.ssh/known_hosts:1
RSA1 host key for aix has changed and you have requested strict checking.
Host key verification failed.
IMO it would be useful for the user to get at least a hint to start
a ssh connection manually in order to see this message. In any case
the user has to edit his known_host file manually.
[...]
>>
>> No, this error is still present. You get the error message, but the
>> file is already fetched, if you select the file once again in the
>> dired-buffer, the corresponding buffer pops up without further error
>> messages. Selecting another file in the dired-buffer leads to the
>> same error again.
>
> Please try the following patch, or the most recent CVS.
>
Latest CVS is working now. Thank you Kai!
Marco
--
Marco Lonsing
Mathematik XI - Numerik email: Marco.Lonsing@...
Ruhr-Universitaet Bochum phone: +49-234-32-23244
Universitaetsstr. 150 fax : +49-234-32-03244
D-44721 Bochum, GERMANY www : http://www.ruhr-uni-bochum.de/num1/marco/

Kai.Grossjohann@... (Kai Großjohann) writes:
> Marco Lonsing <Marco.Lonsing@...> writes:
>
>> No there is no question I meant the situation when an admin has
>> installed new host keys. In this case ssh stops with the following
>> output:
>>
>> Warning: Server lies about size of server host key: actual size is 1023 bits vs. announced 1024.
>> Warning: This may be due to an old implementation of ssh.
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> @ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> The RSA1 host key for aix has changed,
>> and the key for the according IP address 134.147.215.35
>> is unchanged. This could either mean that
>> DNS SPOOFING is happening or the IP address for the host
>> and its host key have changed at the same time.
>> Offending key for IP in /home/marco/.ssh/known_hosts:3
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
>> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
>> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
>> Someone could be eavesdropping on you right now (man-in-the-middle attack)!
>> It is also possible that the RSA1 host key has just been changed.
>> The fingerprint for the RSA1 key sent by the remote host is
>> c9:5c:6f:69:0d:65:c9:97:dd:9f:f7:ca:f7:82:f7:58.
>> Please contact your system administrator.
>> Add correct host key in /home/marco/.ssh/known_hosts to get rid of this message.
>> Offending key in /home/marco/.ssh/known_hosts:1
>> RSA1 host key for aix has changed and you have requested strict checking.
>> Host key verification failed.
>>
>> IMO it would be useful for the user to get at least a hint to start
>> a ssh connection manually in order to see this message. In any case
>> the user has to edit his known_host file manually.
>
> I have now added "Host key verification failed." as a "wrong
> password" regexp, and I have changed Tramp to show the *tramp/foo*
> buffer when a wrong password message is seen. Please try the current
> CVS or the following patch. Does it do the trick?
>
Yes this works! Thank you.
Marco
--
Marco Lonsing
Mathematik XI - Numerik email: Marco.Lonsing@...
Ruhr-Universitaet Bochum phone: +49-234-32-23244
Universitaetsstr. 150 fax : +49-234-32-03244
D-44721 Bochum, GERMANY www : http://www.ruhr-uni-bochum.de/num1/marco/