On 9/17/2019 2:52 PM, Jeffrey Walton wrote:
> Hi Everyone,
>
> Please forgive my naive question...
>
> We would like to backup the Test PIV Cards prior to use. We think
> there's a good chance we will break a few of them during testing.
What are you planing on testing? PIV cards in users hands are esentially
read only. If you want to test writing objects or generating key
you will need to know the 9B key. (See below too.)
>
> Searching the group did not return any results. Search is finding some
> hits for backing up smart cards using specific equipment from certain
> manufacturers, but I have not found generic instructions.
There are no generic PIV specs for backup. Looking close at the NIST sp800-73-*
specifications, you will note that card provioning is really left up to
card vendors. sp800-73-* does define GENERATE_KEYPAIR and PUT_DATA but requires
at least the 9B key. Depending on the card vendor, they may or may not use
the 9B admin key.
>
> Does NIST have a procedure to back up the test cards? If so, could
> someone point me to the document or procedure?
>
> (Part of me feels it should not be possible to export the private key
> associated with a certificate or public key. The only way to know for
> sure is ask the folks who created the cards).
You will also note that each set of Test PIV Cards are duplicates so there is a way
to write keys to teh card, which is not in sp800-73-* But each crd vendor may or may
not have a way to export a key that was generated on the card.
Also note that in the test cards I have from years ago, two different types
of cards where used from two different vendors. Your sent may have different cards
from what I have abd from different vendors.
If you want to do real testing of writting, get a set of blank PIV cards from
some vendor who will provide you with the instrictions on how to unlock the cards
and provide you with the keys for you batch of cards.
ALso see
https://github.com/OpenSC/OpenSC/wiki/US-PIV which is wht I have been inolved with.
>
> Thanks in advance,
>
> Jeffrey Walton
>
--
Douglas E. Engert <
DEEn...@gmail.com>