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.

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

Introduce applet lifecycle support and pre-perso locking #26

Open
makinako opened this issue Aug 27, 2020 · 0 comments
Open

Introduce applet lifecycle support and pre-perso locking #26

makinako opened this issue Aug 27, 2020 · 0 comments
Assignees

Comments

@makinako
Copy link
Owner

At present, pre-personalisation can occur post-issuance. In some scenarios it is desirable to lock this down so that the applet filesystem is defined once and then locked:

Suggestion:

  1. Support the GET/SET STATUS commands to progress the applet lifecycle to APPLET_PERSONALIZED
  2. When the applet is in the APPLET_PERSONALIZED state, the putDataAdmin() command is irreversibly disabled
  3. Possibly also lock changeReferenceDataAdmin() as an optional FEATURE_ (as key injection is an expected post-issuance activity for some installs)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant