[ http://issues.apache.org/jira/brows...-108?page=3Dall ]
=20
Emmanuel Lecharny resolved DIRSNICKERS-108:
-------------------------------------------

Resolution: Fixed

Ok, with huge modifications, this problem has been fixed !

Basically, using previous BER code wrote for Snickers was much easier than =
trying to bringing back from university all this binary theory I have forgo=
tten ...

It drove me to modify the encoding and decoding of Integer, and had a side =
effect on Boolean decoding.

Everything should be on track again...

Thanks J=C3=A9r=C3=B4me for the sharp reports, and for the time you dedicat=
ed on this f****g problem !

btw, using BigInteger is not an option : it's 24x slower than doing it the =
way Snickers does ;)

WARNING : This is NOT compliant with ASN.1 BER, as the biggest ASN.1 BER in=
teger is supposed to be 256^126 - 1

> Wrong int encoding in Value
> ---------------------------
>
>          Key: DIRSNICKERS-108
>          URL: http://issues.apache.org/jira/browse/DIRSNICKERS-108
>      Project: Directory ASN1
>         Type: Bug
>   Components: BER Runtime
>     Reporter: J=C3=A9r=C3=B4me Baumgarten
>     Assignee: Emmanuel Lecharny
>     Priority: Blocker
>  Attachments: Value.patch
>
> Hi,
> Encoding is buggy for int value in the org.apache.asn1new.ber.tlv.Value c=
lass. The affected methods are :
> * public static int getNbBytes( int value )
> * public static byte[] getBytes( int value )
> Regards,
> J=C3=A9r=C3=B4me

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]