luo980/curl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge 0e035f60e7 into b4834a7d6d

Browse Source
This commit is contained in:
Monochrome 2025-03-01 02:30:06 +00:00 committed by GitHub
commit 08bd48d903
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/cmdline-opts/cert.md
View File

@ -58,3 +58,9 @@ usually a SHA-1 hex string which you can see in certificate details. Following
store locations are supported: *CurrentUser*, *LocalMachine*,
*CurrentService*, *Services*, *CurrentUserGroupPolicy*,
*LocalMachineGroupPolicy* and *LocalMachineEnterprise*.
# Using OpenSSL Engine with TPM 2.0
To use an OpenSSL engine with a TPM 2.0,
use this command
`curl --key /path/to/key.tss --cert /path/to/cert.crt https://my-server.com/download/url`.

7
docs/cmdline-opts/key.md
View File

@ -27,8 +27,15 @@ private key located in a PKCS#11 device. A string beginning with `pkcs11:` is
interpreted as a PKCS#11 URI. If a PKCS#11 URI is provided, then the --engine
option is set as `pkcs11` if none was provided and the --key-type option is
set as `ENG` or `PROV` if none was provided (depending on OpenSSL version).
For
If curl is built against Secure Transport or Schannel then this option is
ignored for TLS protocols (HTTPS, etc). Those backends expect the private key
to be already present in the keychain or PKCS#12 file containing the
certificate.
# Using OpenSSL Engine with TPM 2.0
To use an OpenSSL engine with a TPM 2.0,
use this command
`curl --key /path/to/key.tss --cert /path/to/cert.crt https://my-server.com/download/url`.