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

Document clearly how Mbed Crypto provider keys are stored #373

Closed
ionut-arm opened this issue Mar 29, 2021 · 2 comments
Closed

Document clearly how Mbed Crypto provider keys are stored #373

ionut-arm opened this issue Mar 29, 2021 · 2 comments
Assignees
Labels
bug Something isn't working documentation security Issues related to the security and privacy of the service

Comments

@ionut-arm
Copy link
Member

The documentation for what gets stored on disk for the Mbed Crypto provider isn't clear enough, as it could be misunderstood (based on the store_path of the KeyInfoManager) that the keys are stored along with their mappings.

In reality, the keys are stored locally in the working directory of the process using the Mbed Crypto library. This can be changed at compile time (see this) - maybe we could also include this as part of our build, but the main point is that the behaviour should be described more thoroughly somewhere, preferably both in the book and in the config file

@ionut-arm ionut-arm added bug Something isn't working security Issues related to the security and privacy of the service documentation labels Mar 29, 2021
@ionut-arm ionut-arm self-assigned this Mar 29, 2021
@hug-dev
Copy link
Member

hug-dev commented Mar 29, 2021

Related to #53

@ionut-arm
Copy link
Member Author

Solved in the two PRs linked above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation security Issues related to the security and privacy of the service
Projects
None yet
Development

No branches or pull requests

2 participants