search for: ssh_key_bits_reserv

Displaying 3 results from an estimated 3 matches for "ssh_key_bits_reserv".

Did you mean: ssh_key_bits_reserved
2001 Feb 08
1
ssh1 keyexchange problem ?
Hi, Has anybody produced diffs for openssh-2.3.0p1 for the rsa keyexchange problem that Core-SDI described ? ( I noticed that fix is already in openbsd tree ). -Jarno -- Jarno Huuskonen - System Administrator | Jarno.Huuskonen at uku.fi University of Kuopio - Computer Center | Work: +358 17 162822 PO BOX 1627, 70211 Kuopio, Finland | Mobile: +358 40 5388169
2001 Feb 05
1
I have an odd OpenSSH compatablity issue
...lni /proc' disabled (badness 2) debug: Command 'ps -efl' disabled (badness 2) debug: Command 'ipcs -a' disabled (badness 2) debug: Seeded RNG with 35 bytes from programs debug: Seeded RNG with 3 bytes from system calls respond_to_rsa_challenge: public_key 895 < host_key 768 + SSH_KEY_BITS_RESERVED 128 debug: Calling cleanup 0x3a08c(0x0) debug: Calling cleanup 0x3f4b0(0x0) debug: writing PRNG seed to file /home1/sa/.ssh/prng_seed
2001 Feb 19
1
Dubious use of BN_num_bits in sshconnect1.c
...nect to a SSH 1.2.20 server, with messages such as the following: Warning: Server lies about size of server public key: actual size is 1151 bits vs. announced 1152. Warning: This may be due to an old implementation of ssh. respond_to_rsa_challenge: public_key 1151 < host_key 1024 + SSH_KEY_BITS_RESERVED 128 ..and a resulting refusal to continue. I've done a bit of digging in the source, and have found the source of the problem to be the use of BN_num_bits to determine the length of the keys received in sshconnect1.c. The problem is that BN_num_bits does not return the number of signifi...