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

Update HOWTO.md #411

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Update HOWTO.md #411

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
10 changes: 7 additions & 3 deletions HOWTO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,9 @@ pkcs11-module-init-args = <initialization string here>

Once the section is properly constructed add the following statement to the
provider section. If a provider section does not exist make sure to create one
with all the needed providers (at least the default provider will be needed):
with all the needed providers (at least the default provider will be needed -
remember to activate it, otherwise the _openssl_ command will not behave
correctly):

```
[openssl_init]
Expand Down Expand Up @@ -65,8 +67,10 @@ $ openssl pkey -in pkcs11:id=%01 -pubin -pubout -text
### Specifying keys

When the pkcs11-provider is in use keys are specified using pkcs11 URIs as
defined in RFC7512. In general keys are either identified by a binary ID, or by
a label (called "object" in pkcs11 URIs).
defined in RFC7512. In general keys are either identified by a percent-encoded
binary ID, or by a label (called "object" in pkcs11 URIs). The command
`pkcs11-tool --module /path/to/pkcs11-driver.so --list-objects` can be used to
find identifiers for your keys.

Example:
```
Expand Down
Loading