Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Interoperability with OpenSSH3.4p1 and OpenSSH4.3p2

Subject: Interoperability with OpenSSH3.4p1 and OpenSSH4.3p2
Date: Tue, 13 Feb 2007 10:27:34 +0000 (GMT)
Hi,

I am working on an SSH implementation that has to
connect to a SSH
server. I find that the length of the DH modulus
contained in
SSH2_MSG_KEX_DH_GEX_GROUP (as defined by RFC 4419) 
message sent by
the server for a 2048-bit DH key scenario is 399 bytes
as opposed to
256 bytes. This is causing trouble with the client as
the length is
uncharacteristic of the known DH group 14 .

However for a scenario of a 1024-bit key, as expected
a 128 byte
modulus is sent by the server in the
SSH2_MSG_KEX_DH_GEX_GROUP
message.

Could some one explain this deviation from standard?
Am i missing the
math involved in the size of the modulus that is sent
across?

Please clarify,
Regards,
Naveen



                
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/

<Prev in Thread] Current Thread [Next in Thread>
  • Interoperability with OpenSSH3.4p1 and OpenSSH4.3p2, naveen t <=