With bounds checking patch for gcc-3.1 problems if using AES

Gert Doering gert at greenie.muc.de
Fri Jul 12 23:50:42 EST 2002


Hi,

On Fri, Jul 12, 2002 at 12:43:30PM +0200, Markus Friedl wrote:
> did anyone check this?

I tried it, but it doesn't solve my problem (and thinking about it, there
is no way how it could).

My problem is this:

gert at moebius:/tmp$ ssh-keygen -t dsa -f /tmp/dsa-key -N ""
Generating public/private dsa key pair.
Your identification has been saved in /tmp/dsa-key.
Memory fault
gert at moebius:/tmp$ ssh-keygen -t rsa -f /tmp/rsa-key -N ""
Generating public/private rsa key pair.
Your identification has been saved in /tmp/rsa-key.
Memory fault
gert at moebius:/tmp$ ls -l *sa-key*
-rw-------  1 gert  wheel  668 Jul 12 15:47 dsa-key
-rw-r--r--  1 gert  wheel    0 Jul 12 15:47 dsa-key.pub
-rw-------  1 gert  wheel  887 Jul 12 15:47 rsa-key
-rw-r--r--  1 gert  wheel    0 Jul 12 15:47 rsa-key.pub

Same problem in ssh:

gert at moebius:/tmp$ ssh -v -2 moebius2
...
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
The authenticity of host 'moebius2 (195.30.1.100)' can't be established.
RSA key fingerprint is 54:0c:18:e4:4a:4a:23:8d:c2:c9:5b:2e:1c:8b:24:4a.
Are you sure you want to continue connecting (yes/no)? yes
Memory fault

- all sorts of key handling with DSA or RSA2 keys leads to core dumping,
while everything done with RSA1 keys works just fine.  "ssh -1" has 
no problems whatsoever either.

Happens *only* on FreeBSD 2.1.x machines, with x > 5.

As this machine will go out of service "soon" anyway, I haven't done any
in-depth debugging yet.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert.doering at physik.tu-muenchen.de



More information about the openssh-unix-dev mailing list