Kim O'Sullivan

This has been implemented for the upcoming v2.0.0 FIPS version in the form of basic platform abstraction. To summarise, there is a PIVPlatform class created for each supported platform and...

As described in issue #60, the expectation is that the values are already constructed with the required class/multibyte indicators. it makes for a terrible general purpose TLV encoder but does...

This is correct, however there is a rationale for it (good or not). I've deliberately made the TLVReader class as bare-bones as possible and this includes parsing of the tag...

From OF201's perspective: * Lengths >= 128 are a-ok, it just needs to fit into a short-form RAPDU. * The AC tag is conditional, which we interpret as 'Optional, but...

Yes now having a read through the 7816 wording is actually very clear. OF201 was implemented only from the SP800-73 wording and this is in contradiction with the ISO standard...

> In terms of "be conservative in what you do, be liberal in what you accept from others", would the current OF201 implementation actually violate ISO 7816 in any way?...

Just from a slightly different perspective, some useful reasons for having all the supported mechanisms listed are: - it provides the possibility of turning on and off mechanism support by...

We are in sync :) I've just sent an email an hour ago to NIST asking for an indicator of any upcoming mechanism changes. Let's see what we get. On...

We have some answers from NIST: 1. Could I confirm that the presence of the AC tag in the PIV FCI should be conforming to the definition in ISO 7816-4...

> Who at NIST responded to the inquire(s)? I can try asking the same type of question and point out there are three of us @arekinath, @mistial-dev, @makinako and @dengert...