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

docs: fix some typos flagged by Lintian #519

Merged
merged 1 commit into from
Feb 11, 2025
Merged

docs: fix some typos flagged by Lintian #519

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
10 changes: 5 additions & 5 deletions docs/provider-pkcs11.7
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
.\"
.TH "provider\-pkcs11" "7" "" "" "Configuration directives"
.SH NAME
pkcs11\-provider \- An OpenSSL provider that allows to directly
pkcs11\-provider \- An OpenSSL provider that allows one to directly
interface with pkcs11 drivers.
.SH DESCRIPTION
Starting with version 3.0 the OpenSSL project introduced a new modular
Expand Down Expand Up @@ -60,7 +60,7 @@ cat /etc/pki/pin.txt
123456
.EE
.SS pkcs11\-module\-allow\-export
Whether the pkcs11 provider will allow to export public keys through
Whether the pkcs11 provider will allow one to export public keys through
OpenSSL.
OpenSSL often tries to export public keys from non\-default providers to
the default provider, and then use OpenSSL own functions to handle
Expand Down Expand Up @@ -109,7 +109,7 @@ Example:
\f[CR]pkcs11\-module\-cache\-pins = cache\f[R] (Will cache a pin that
has been entered manually)
.SS pkcs11\-module\-cache\-sessions
Allows to tune how many pkcs11 sessions may be kept open and cached for
Allows one to tune how many pkcs11 sessions may be kept open and cached for
rapid use.
This parameter is adjusted based on the maximum number of sessions the
token declares as supported.
Expand Down Expand Up @@ -182,7 +182,7 @@ Example:
\f[CR]pkcs11\-module\-quirks = no\-deinit no\-operation\-state\f[R]
(Disables deinitialization, blocks context duplication)
.SS pkcs11\-module\-block\-operations
Allows to block specific \[lq]provider operations\[rq] even if the token
Allows one to block specific \[lq]provider operations\[rq] even if the token
actually supports the necessary mechanisms.
This is useful to work around cases where one wants to enforce use of
the token for all operations by setting ?provider=pkcs11 in the default
Expand Down Expand Up @@ -263,7 +263,7 @@ URI and produce a PEM file that references it.
Note that storing PINs within these PEM files is not secure.
These files are not encrypted.
.PP
The follwing command can be used to list all keys on a token and print
The following command can be used to list all keys on a token and print
their identifying URI:
.IP
.EX
Expand Down
10 changes: 5 additions & 5 deletions docs/provider-pkcs11.7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

NAME
====
pkcs11-provider - An OpenSSL provider that allows to directly interface
pkcs11-provider - An OpenSSL provider that allows one to directly interface
with pkcs11 drivers.


Expand Down Expand Up @@ -72,7 +72,7 @@ cat /etc/pki/pin.txt

## pkcs11-module-allow-export

Whether the pkcs11 provider will allow to export public keys through
Whether the pkcs11 provider will allow one to export public keys through
OpenSSL.
OpenSSL often tries to export public keys from non-default providers to
the default provider, and then use OpenSSL own functions to handle
Expand Down Expand Up @@ -128,7 +128,7 @@ Example:
(Will cache a pin that has been entered manually)

## pkcs11-module-cache-sessions
Allows to tune how many pkcs11 sessions may be kept open and cached for
Allows one to tune how many pkcs11 sessions may be kept open and cached for
rapid use. This parameter is adjusted based on the maximum number of
sessions the token declares as supported. Note that the login session is
always cached to keep the token operable.
Expand Down Expand Up @@ -207,7 +207,7 @@ Example:
(Disables deinitialization, blocks context duplication)

## pkcs11-module-block-operations
Allows to block specific "provider operations" even if the token actually
Allows one to block specific "provider operations" even if the token actually
supports the necessary mechanisms. This is useful to work around cases
where one wants to enforce use of the token for all operations by setting
?provider=pkcs11 in the default properties but wants an exception for a
Expand Down Expand Up @@ -295,7 +295,7 @@ In tools/uri2pem.py there is a sample python script that can take a key
URI and produce a PEM file that references it. Note that storing PINs
within these PEM files is not secure. These files are not encrypted.

The follwing command can be used to list all keys on a token and print
The following command can be used to list all keys on a token and print
their identifying URI:

openssl storeutl -keys -text pkcs11:
Expand Down
Loading