The key that's generated is a 56 byte hex pair encoded string. 111 'bytes'
will still convert (with hex) to 56 bytes using this (in Perl, just ripped
it from the client code):
$cipher = new Crypt::CBC(pack('H*', $OPENSRS{private_key}),
$OPENSRS{crypt_type});
--Charles Daminato Tucows Product Manager (ccTLDs) chuck@tucows.com
Matters could get so confusing at work that it is actually laughable. - From National Post Horoscope for Gemini, Nov. 1st 2000
-----Original Message----- From: owner-dev-list@opensrs.org [mailto:owner-dev-list@opensrs.org]On Behalf Of MacNeil, James Sent: November 10, 2000 5:50 PM To: 'dev-list@opensrs.org' Subject: Key length
Why does the SRS admin page generate keys that are either 111 or 112 bytes long?
We're using our own C program to process registrations and are interested in knowing how Perl handles binary conversion of a 111 byte "hex" key. Does Perl ignore the missing byte and append a zero?
If not, how does Perl handle the conversion of 2 characters into a byte when one of the characters is missing?
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:36:03 EDT