OpenSSH_3.7.1p2 Floating point exception on Opteron

[Darren Tucker]

Dan Pelleg wrote:
> I'm getting a floating point exception from ssh on an opteron running Linux
> (in 64 bit). It happens only when I ssh out to a server not supporting
> SSHv2 and when its public key is not already in the key file. Right after I
> answer "yes" to the "Are you sure?" prompt I get the exception.
> 
> Here is the stack trace:
> 
> Program received signal SIGFPE, Arithmetic exception
> 0x0000002a95a0d58c in bn_div_words () from /usr/lib/libcrypto.so.0.9.7
> (gdb) bt
> #0  0x0000002a95a0d58c in bn_div_words () from /usr/lib/libcrypto.so.0.9.7
> #1  0x0000002a95a0a905 in BN_div_word () from /usr/lib/libcrypto.so.0.9.7
> #2  0x0000002a95a09a09 in BN_bn2dec () from /usr/lib/libcrypto.so.0.9.7
> #3  0x000000000041ec59 in write_bignum (f=0x5567c0, num=0x8ac7230489e80000) at key.c:368
> #4  0x000000000041f060 in key_write (key=0x556050, f=0x5567c0) at key.c:504
> #5  0x0000000000418971 in add_host_to_hostfile (

This looks like an error inside OpenSSL.  Does OpenSSL's self-test (ie 
"make test") pass?

> I see a similar report at:
> http://www.mindrot.org/pipermail/openssh-unix-dev/2004-January/020326.html
> 
> Is this the same issue?

No.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.