Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

design: countermeasure #1

Open
martinpaljak opened this issue Jan 25, 2023 · 1 comment
Open

design: countermeasure #1

martinpaljak opened this issue Jan 25, 2023 · 1 comment

Comments

@martinpaljak
Copy link
Collaborator

Normally a card application implements certain countermeasures to protect contained assets from attacks. Like blocking a PIN code and thus use of a card until a PUK/unblock, deleting sensitive assets or terminating the card altogether. No PUK has been in design this far (maybe it should be added?) and wiping phonons is not what we want. Thus the only active countermeasure for attack detection is "do not allow to send phonons". Receiving and revealing phonons is not affected.
@martinpaljak
Copy link
Collaborator Author

Added PUK in #3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martinpaljak