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

Confusing naming of config option for PIN-protected certificates #2597

Closed
xhanulik opened this issue Aug 30, 2022 · 0 comments · Fixed by #3070
Closed

Confusing naming of config option for PIN-protected certificates #2597

xhanulik opened this issue Aug 30, 2022 · 0 comments · Fixed by #3070

Comments

@xhanulik
Copy link
Contributor

Problem Description

OpenSC configuration allows adjusting the handling of PIN-protected certificates. This is done by private_certificate option with values protected, declassify and ignore. However, the naming private_ may confuse users with private data caching and its restriction (use_file_caching option), which is targeted by #2588.

Proposed Resolution

Rename the private_certificate option to distinguish between handling PIN-protected certificates and caching private data (maybe something like pin_protected_certificate to get rid of private_).
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

Successfully merging a pull request may close this issue.

Rename configuration option private_certificate to pin_protected_certificate xhanulik/OpenSC
1 participant
@xhanulik