Thomas Quinot wrote:
> Le 2001-05-13, Peter Wemm �crivait :
>
> > The simplest thing is to do a ssh-keygen to generate a new RSA key and
> > update ~/.ssh/authorized_keys2 once per remote machine that you connect
> > to. Once that is done, it never bothers you again. You can change
> > /etc/ssh/ssh_config so that it says 'Protocol 1,2', but that is avoiding
> > the problem rather than using the more robust, cryptographically secure
> > sshv2 wire protocol.
>
> Ah. This seems to work around the very unfortunate situation described in
> PR bin/27264. It seems very strange that one has to change the setup
> on the *server* side to work around a regression on the client side.
>
> Why cannot one use the same RSA public key for v1 and v2 client
> authentication?
That is something that I'd like to know too. RSA keys are RSA keys,
regardless of how they are encoded.
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
