But for sending them through mail you must have transferred
them from the server to your machine. During this transfer
binary format needs to used otherwise the keys get
transferred. I had been getting the same errors when the
keys were taken on my system in ascii format. Or the issue
might be with dsa on one side and rsa on the other.
But since you can transfer the file to other server with the
same combination, it doesn't exactly seem to be the problem.
Cheers,
Varun
-----Original Message-----
From: Frans Englich [mailto:frans.englich@telia.com]
Sent: 26 May 2006 15:29
To: varun
Cc: secureshell@securityfocus.com
Subject: Re: Publick key authentication problem
On Friday 26 May 2006 14:10, varun wrote:
Were bthe keys ftped to your system in ascii or binary
format.
They weren't transfered with FTP, they were sent via mail. I
don't see how this could have caused trouble, especially
since the public key is base64 encoded from the start. Also,
as written in the previous mail, for the server where SSH
works I also sent the key via mail.
Cheers,
Frans
============================================================================================================================
Tech Mahindra, formerly Mahindra-British Telecom.
Disclaimer:
The contents of this E-mail (including the contents of the enclosure(s) or
attachment(s) if any) are privileged and confidential material of Tech Mahindra
and should not be disclosed to, used by or copied in any manner by anyone other
than the intended addressee(s). In case you are not the desired addressee, you
should delete this message and/or re-direct it to the sender. The views
expressed in this E-mail message (including the enclosure(s) or attachment(s)
if any) are those of the individual sender, except where the sender expressly,
and with authority, states them to be the views of Tech Mahindra.
This e-mail message including attachment/(s), if any, is believed to be free of
any virus. However, it is the responsibility of the recipient to ensure that it
is virus free and Tech Mahindra is not responsible for any loss or damage
arising in any way from its use.
============================================================================================================================
