-----BEGIN PGP SIGNED MESSAGE-----
At 02:11 PM 11/9/99 -0600, Chuck Milam wrote:
>
>I have several Red Hat Linux machines here running ssh 1.2.27 that's
been
>compiled and installed from the source tarballs. In the interest of
>easier administration, I thought I'd try out the SSH RPMs from
replay.com.
>
>After building and installing ssh-1.2.27-5us.src.rpm, when I try to
>connect to a machine that's had ssh installed from RPM from a machine
that
>has ssh installed from source, I cannot connect. This message
appears in
>the system log of the machine with the RPM/SSH installation:
>
>sshd[7154]: fatal: RSA key has too many bits for RSAREF to handle
(max
>1024).
Take a look at this part of the FAQ:
http://www.tigerlair.com/ssh/faq/ssh-faq-7.html#ss7.2.6
>Huh? All I did when installing ssh from source tarballs was a
simple:
>
>configure
>make
>make install
>
>The question: What is different about the source installation that
causes
>this incompatibility with the RPM installation of SSH? Is there some
>setting in the RPM spec file that limits the size of the RSAREF
library
>when building the SRPM? Anyone else seen this behavior?
The limitation is with RSAREF. RSAREF may make SSH1 legal to run in
the US without
violating the US patent laws. Because RSAREF is an educational
toolkit, RSA limited its
key sizes to 768 bits.
Most people who use SSH without RSAREF use 1024 bit keys, so that's
why you're having the
problem connecting.
RSA no longer supports RSAREF, btw, or even admits to its existance.
Hope that helps! :)
- -Anne
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2
iQCVAwUBOCiXY5R9aHf4XCixAQEE8QP/VQs7eavkHEdmKOgjBwye/g7fMhym1Kxn
pQ1Ys0FYEkouwpVzkX4FJz6qpJWQ/T2QcxCGQ9G1Ow0qWLzHGuOVu2Ww3mAOOTya
E62hvnDdeE1b1m86kG8XIh7uscIV+1iPgg6jH1e6kF6TtGItPYrXNC9OC/Egbfnb
NTAmv8uBFAc=
=ajPx
-----END PGP SIGNATURE-----
--
Anne Carasik
Consulting Engineer
SSH Communications Security Inc.
Email: [EMAIL PROTECTED]
#include <standarddisclaimer.h>
