Jordan Sautreau

Hi Daniel, I am using iso1 codec. The issue is not encoding/decoding directly but on computing the signature. The payload is encoded and received by a server using exificient. When receiving the request, the server decodes successfully the request. Then it has to encode the payload (without the signature) to check if the signature is correct. So it encodes back the content to compute a hash. That is when we face the issue because the payload is different (1 byte more for each root certificate) so...

Hi Daniel, I am using iso1 codec. The issue is not encoding/decoding directly but on computing the signature. The payload is encoded and received by a server using exificient. When receiving the request, the server decodes successfully the request. Then it has to encode the payload (without the signature) to check if the signature is correct. So it encodes back the content to compute a hash. That is when we face the issue because the payload is different (1 byte more for each root certificate) so...

Hello, We have found an issue in the encoding. It indeed adds a byte because of the encoding on 7 bits and 1 bit more to indicate if the encoding is done or not. For example, if the serial number is 9: This is 0b00001001 in binary. So we need 4 bits to encode it. Then openv2g considers that we need a byte, then 8 bits. As the bits are encoded 7 by 7, openv2g considers that we need 2 bytes to encode this number. We have patched this and tested it sucessfully. We might share a fix proposal for this...