Replies: 1 comment 2 replies
-
|
This is a very vendor-specific issue. Do analyze the product documentation to figure out if the pre-personalization integrity satisfies your requirements, and choose a vendor (and a product) without any backdoors. Generally speaking: a rogue vendor is like a rogue maid - not only can they claim to be world record holder in speed-cleaning when they are not, they can also steal everything AND (theoretically) can also hit you with an axe. What decisions you make based on this knowledge, is up to your own judgement. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone!
I've been looking at Java Cards for use with open source applets such as FIDO2Applet, and I'm wondering how secure this type of usage really is.
First of all, it's unclear to me whether unfused cards can be set to
OP_READYand later states. The lifecycle state and fuse state are two different properties, but as far as I can tell, no operations can be performed by GlobalPlatformPro on an unfused card, and once the card has been fused, there's no way to go back to the pre-initialization state—is that assumption correct?My specific concern is about whether a rogue card vendor would theoretically be able to sell cards in
OP_READYand provide the regular keys (ENC, MAC and DEK) while still keeping a Transport Key (TK) as a backdoor that would be able to reset the card into a previous state in the lifecycle and change its keys.I'd love any information about this!
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions