[opensc-devel] [Muscle] secure pin verify/modify and byte ordering

Martin Preuss aquamaniac at gmx.de
Sat Mar 21 08:13:32 PDT 2009


Hi again,

On Samstag, 21. März 2009, Martin Preuss wrote:
[...]
> The statement "Byte ordering is decided by machine architecture" is stupid
> in itself: How would the reader know what architecture the device is
> connected to? With this change the firmware is now supposed to somehow
> acquire that knowledge in order to detect how the multi-byte values of the
> CCID structures are to be interpreted...
[...]

Ah, sorry, I see: This was only about the PC/SC structures, not the CCID 
structures, right?

Anyway, I don't think it was a good idea to change the statement about 
endianess, since now application *and* driver have to know what version of 
the PC/SC specs the other end uses...


Regards
Martin


-- 
"Things are only impossible until they're not"

Martin Preuss - http://www2.aquamaniac.de/
AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/



More information about the Muscle mailing list