search for: buffer_get_bignum

..._bignum(buffer, key->e); + buffer_put_bignum(buffer, key->n); + buffer_put_bignum(buffer, key->d); + buffer_put_bignum(buffer, key->iqmp); + buffer_put_bignum(buffer, key->p); + buffer_put_bignum(buffer, key->q); +} + +static void +buffer_get_key_rsa(Buffer *buffer, RSA *key) +{ + buffer_get_bignum(buffer, key->e); + buffer_get_bignum(buffer, key->n); + buffer_get_bignum(buffer, key->d); + buffer_get_bignum(buffer, key->iqmp); + buffer_get_bignum(buffer, key->p); + buffer_get_bignum(buffer, key->q); + rsa_generate_additional_parameters(key); +} + +static void +buffer_put_key...

...ersion string SSH-2.0-OpenSSH_7.3 ssh_exchange_identification: read: Connection reset by peer /var/log/messages: Aug 2 17:35:07 host102 sshd[7449]: Server listening on 0.0.0.0 port 222. Aug 2 17:35:07 host102 sshd[7449]: Server listening on :: port 222. Aug 2 17:36:03 host102 sshd[7455]: error: buffer_get_bignum_ret: \n incomplete message Aug 2 17:36:03 host102 sshd[7455]: fatal: buffer_get_bignum: buffer \n error The code after line 1111 in sshd.c (buffer_get_bignum) seems to be not adequate any more. I suppose the error will also show up on Centos. Best regards Rainer

...u_int value) { Index: bufaux.h =================================================================== RCS file: /cvs/src/usr.bin/ssh/bufaux.h,v retrieving revision 1.17 diff -u -r1.17 bufaux.h --- bufaux.h 18 Mar 2002 17:25:29 -0000 1.17 +++ bufaux.h 19 Apr 2002 12:55:56 -0000 @@ -23,6 +23,9 @@ void buffer_get_bignum(Buffer *, BIGNUM *); void buffer_get_bignum2(Buffer *, BIGNUM *); +u_short buffer_get_short(Buffer *); +void buffer_put_short(Buffer *, u_short); + u_int buffer_get_int(Buffer *); void buffer_put_int(Buffer *, u_int);

...u_int value) { Index: bufaux.h =================================================================== RCS file: /cvs/src/usr.bin/ssh/bufaux.h,v retrieving revision 1.17 diff -u -r1.17 bufaux.h --- bufaux.h 18 Mar 2002 17:25:29 -0000 1.17 +++ bufaux.h 19 Apr 2002 12:55:56 -0000 @@ -23,6 +23,9 @@ void buffer_get_bignum(Buffer *, BIGNUM *); void buffer_get_bignum2(Buffer *, BIGNUM *); +u_short buffer_get_short(Buffer *); +void buffer_put_short(Buffer *, u_short); + u_int buffer_get_int(Buffer *); void buffer_put_int(Buffer *, u_int);

Hi, 1. I think you should apply the attached patch to openssh-2.9p1, otherwise ssh-keyscan on linux boxes with glibc-2.1 will experience enormous timeout delays. 2. Is there a program like ssh-keyscan for the Version2 (dsa and rsa) keys?? regards Peter Breitenlohner <peb at mppmu.mpg.de> -------------- next part -------------- diff -ur openssh-2.9p1.orig/ssh-keyscan.c

...SH_SMSG_PUBLIC_KEY) { - error("%s: invalid packet type", host); + error("%s: invalid packet type", c->c_name); buffer_clear(&msg); - return; + return NULL; } buffer_consume(&msg, 8); /* cookie */ @@ -270,10 +292,70 @@ (void) buffer_get_int(&msg); buffer_get_bignum(&msg, rsa->rsa->e); buffer_get_bignum(&msg, rsa->rsa->n); + buffer_clear(&msg); + + return (rsa); +} + +static int +hostjump(Key *hostkey) +{ + longjmp(kexjmp, (int)hostkey); +} + +int +ssh2_capable(int remote_major, int remote_minor) +{ + switch (remote_major) { + case...

...entering fd = 8 config len 285 debug3: ssh_msg_send: type 0 debug3: send_rexec_state: done debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8 -------------- next part -------------- Aug 3 03:31:56 host102 sshd[7449]: Received signal 15; terminating. Aug 3 04:03:19 host102 sshd[8897]: error: buffer_get_bignum_ret: incomplete message Aug 3 04:03:19 host102 sshd[8897]: fatal: buffer_get_bignum: buffer error -------------- next part -------------- diff ../openssh-7.3p1.nossh1/config.h config.h 1722c1722 < /* #undef WITH_SSH1 */ --- > #define WITH_SSH1 1

...case I'm surprised it starts at > all. Exactly how are you starting sshd? > >> Aug 2 17:35:07 host102 sshd[7449]: Server listening on 0.0.0.0 port 222. >> Aug 2 17:35:07 host102 sshd[7449]: Server listening on :: port 222. >> Aug 2 17:36:03 host102 sshd[7455]: error: buffer_get_bignum_ret: \n >> incomplete message > > that might be the newline confusing the re-exec protocol although I'm not sure. > > Please including complete debug logs for both client and server. > The newlines are *not* in the real calls, but are all inserted by me into the email to...