NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Matts (1087)
Matts
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
Friday April 12, 2002
08:23 AM
OpenSSH
The public keys that openssh generates aren't compatible with those accepted by commercial ssh. This took us quite some time to figure out. I wonder what the reason for this is.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: OpenSSH (Score:1)
Ilya Martynov (http://martynov.org/ [martynov.org])
Re: OpenSSH (Score:2)
It's the v2 public keys that aren't compatible. See man ssh-keygen for the -e option.
Re: OpenSSH (Score:1)
As for you question about reason for having two incompatible formats. IIRC openssh cannot have its public keys in same format as comercial ssh because it requires using patented algorithms or something like this. One big difference between openssh and comercial implimintations is that openssh uses only "free" algorithms which are not subject of any patent of other similar restrictions.
Ilya Martynov (http://martynov.org/ [martynov.org])
Re: OpenSSH (Score:2)