Skip to content

Add file storage safety to wolfPKCS11 #150

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

Merged
dgarske merged 1 commit into from
Oct 22, 2025
Merged

Add file storage safety to wolfPKCS11 #150

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,8 +98,12 @@ NOTE: In the code, we have embedded a test key. This must be changed for

### WOLFPKCS11_TOKEN_PATH

Path into which files are stored that contain token data.
When not set, defaults to: /tmp
Path into which files are stored that contain token data. If unset, wolfPKCS11
tries, in order, the directory specified by `WOLFPKCS11_TOKEN_PATH`, any store
directory configured by NSS, the user's home directory (`~/.wolfPKCS11` on
POSIX or `%APPDIR%\wolfPKCS11` on Windows), and finally the optional
`WOLFPKCS11_DEFAULT_TOKEN_PATH` build-time setting. There is no fallback to
`/tmp`; deployments must provide a secure storage location explicitly.

### WOLFPKCS11_NO_STORE

Expand Down Expand Up @@ -287,4 +291,3 @@ Adds backend support for TPM 2.0 using wolfTPM. Adds AES CBC key wrap / unwrap s
### wolfPKCS11 Release 1.0 (October 20, 2021)

* Initial PKCS11 support

Loading
Loading