Do you have a question? Post it now! No Registration Necessary. Now with pictures!
September 29, 2003, 6:59 pm
rate this thread
Here's the situation:
* I've installed and configured F-secure ssh ver 3.2.0 (build 7) for
a client as I did for their parent organization. Everything works,
* I use openssh on my Linux laptop and am able to connect w/o issue
after converting my public keys to ssh2 format.
* The client has decided to go with SecureCRT on their Windows systems.
The format of the key seems the same as the standard ssh2 format. When
I transfer the key up to a server, I cannot authenticate using
the public key using either RSA or DSA algorithms.
* I can convert the SecureCRT key to openssh, then back to ssh2 format -
that works. After I send the SecureCRT->openssh->SSH2 key up to
the server I am able to authenticate using public keys.
Is this a known issue and, more importantly, does anyone know a
work around to it? As far as I know, I am the only one w/openssh
here. Although I would like the job security, I'm really not looking
forward to converting public keys for the rest of my career...
Thanks for any hints/tips/suggestions.
Senior UNIX Admin
O'Leary Computer Enterprises
email@example.com (w) 630-904-6098 (c) 630-248-2749
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — Newest thread in » Secure Shell Forum