Re: [ldapext] X.509, RFC4523, RFC3641, big Ints

[Howard Chu <hyc@highlandsun.com>]

Howard Chu wrote:
> I think this is an absolute necessity. In particular, the ASN.1 Integer type 
> does not exclude negative numbers, but it's impossible to determine where the 
> sign bit resides since the word size isn't specified. So the only safe thing 
> to do is to treat it all as unsigned hex.

Bah. I just re-read X.690, never mind... The sign bit is always the top bit of 
the top octet; an unsigned int with all 1's in the top octet just has to 
encoded with a leading all-zero octet.
--
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP     http://www.openldap.org/project/

_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext