-----BEGIN PGP SIGNED MESSAGE-----
This isn't a solution, but if it were me, rather than fight with it,
I'd just do the keygen on another (trusted) machine and copy the new
keys manually to the problem server. This will work fine; just make
sure the perms are set safely on the target when you're done.
Sorry to duck the issue, and apologies also if you already knew you
could do this.
- -d
- --
David Talkington
Community Networking Initiative
[EMAIL PROTECTED]
217-244-1962
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
R. Paulsen Fuchs wrote:
>
>Hello:
>
>Ia m having trouble installing/running ssh/sshd 1.2.6 on a Sparc
>Ultra1 running Solaris 2.5.1, the problem being with ssh-keygen.
>
>I unpacked the distribution and ran ./configure without any
>errors. "make" compiled everything without errors or warnings. However,
>"make install" hangs on:
>
>ssh-keygen -b 1024 -f /etc/ssh_host_key -N:
>
>>Generating 1024 bit host key.
>>Initializing random number generator
>>Generating p: ..................................... (goes on forever).
>
>(running ./ssh-keygen with -b 768 yields the same result)
>
>For some reason it cannot generate a key. I've pasted the output of
>pstack and pmap below. It appears to be stuck at mpz_powm or the rsa
>generation function. gmp2.02 came with the distribution and the
>"make" compiles a libgmp.a and libmp.a in gmp2 subdirectory of the
>source distribution.
>
>We have several Sparc Solaris 2.5.1 -2.7 machines runing ssh/sshd, and
>none of the others have this problem. Copying over a working ssh-keygen
>from one of the other machines and running it yields the same result
>>Generating p: ......................................................
>
>The problem is localized to this one machine, but I can't seem to figure
>out what the difference is, or what's causing it.
>
>
>#./pstack 18610
>18610: ./ssh-keygen -b 1024 -f /etc/ssh_host_key -N
>00025b6c ???????? (efffb480, 0, efffb458, fb9294da, efffb4d0, 10)
>0002025c mpz_powm (efffb4c8, efffb4d0, 40, efffb440, 3eab8, 0) + 47c
>00016560 rsa_random_prime (3ccb8, 28000, 200, 28000, 28000, 1ff) + 1fc
>00016a44 rsa_generate_key (3cc84, 3cb18, 3ccd0, 400, 3cc00, 28) + 90
>00015210 main (3b400, effffcc4, 7, 3cc00, 3b400, 26c00) + 2d8
>000140f4 _start (0, 0, 0, 0, 0, 0) + 5c
>
># ./pmap 18610
>18610: ./ssh-keygen -b 1024 -f /etc/ssh_host_key -N
>00010000 112K read/exec dev: 32,40 ino: 1302930
>0003A000 16K read/write/exec dev: 32,40 ino: 1302930
>0003E000 8K [ heap ]
>0003E000 8K read/write/exec
>EF580000 512K read/exec /usr/lib/libc.so.1
>EF60E000 32K read/write/exec /usr/lib/libc.so.1
>EF616000 8K read/write/exec
>EF630000 16K read/exec /usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1
>EF642000 8K read/write/exec
>/usr/platform/SUNW,Ultra-1/lib/libc_psr.so.1
>EF650000 8K read/write/exec
>EF660000 32K read/exec /usr/lib/libw.so.1
>EF676000 8K read/write/exec /usr/lib/libw.so.1
>EF680000 392K read/exec /usr/lib/libnsl.so.1
>EF6F0000 40K read/write/exec /usr/lib/libnsl.so.1
>EF6FA000 32K read/write/exec
>EF710000 16K read/exec /usr/lib/libmp.so.1
>EF722000 8K read/write/exec /usr/lib/libmp.so.1
>EF730000 16K read/exec /usr/lib/libintl.so.1
>EF742000 8K read/write/exec /usr/lib/libintl.so.1
>EF760000 8K read/exec /usr/lib/libsec.so.1
>EF770000 16K read/write/exec /usr/lib/libsec.so.1
>EF780000 56K read/exec /usr/lib/libsocket.so.1
>EF79C000 8K read/write/exec /usr/lib/libsocket.so.1
>EF7B0000 8K read/exec /usr/lib/libdl.so.1
>EF7C0000 120K read/exec /usr/lib/ld.so.1
>EF7EC000 16K read/write/exec /usr/lib/ld.so.1
>EFFF8000 32K read/write/exec
>EFFF8000 32K [ stack ]
>
>
>Attempting to connect to another machine with the ssh client gets as
>far as "Sent encrypted session key" then fails with an error message
>on the remote machine
>
>"sshd: fatal: rsa_private_decryptO failed"
>
>Again, this appears to be a problem with key generation. We have
>several other solaris boxes running 2.5.1, 2.6 and 2.7. These all
>run ssh/sshd without any problems. I have compared the shared
>libraries used by ssh/sshd on the problematic machine against those on
>another 2.5.1 machine with a working ssh/sshd. The shared libs are
>the same on both machines. I could not find any obvious difference
>between the 2.5.1 machines. I have searched the net and only found
>references to this function being related to the vulnerability in ssh.
>But that was no help in my situation.
>
>Any help greatly appreaciated.
>
>Thanks,
>Mike
>
>---------------------------------------------------------------------
>mike lee [EMAIL PROTECTED]
>
>system administrator
>thirdage media, inc. www.thirdage.com
>---------------------------------------------------------------------
>
>
>
>
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOd6YmL1ZYOtSwT+tAQFluwgAnvr6tfS/JkcXMRWUhcGZIV8x4PkT5OZK
QXMiFCbY9QoX9Hh0UQhYwyiDxLcgFXajl46oE6mkiGRWumMiqbFomdqp6+F3FiHA
YN9GdIMctuRSCRwCwIliE+FgI17793grAT1KxlNXddKeOG9KOkE3zi8e7wDdkvw8
3xTrqhpdgqU8sUAupRtwNhfFvJKPcRxnNs73MzXUFTHsx3flmvo0y0L2OHotKXew
6UandgPFCM+RwhbSUsgyN4BJY18O5hbFe9GPxlIPLCQY+7+XxX9mo/0VjfFkqFt5
msVFcJu90XmXpyfhEHDheKDMCV/5wDVHI9gQrQfpWWlGxdfER2jmQg==
=PWkx
-----END PGP SIGNATURE-----
