mirror of
https://github.com/curl/curl.git
synced 2025-01-24 14:15:18 +08:00
2494b8dd51
- switch all invidual files documenting command line options into .md, as the documentation is now markdown-looking. - made the parser treat 4-space indents as quotes - switch to building the curl.1 manpage using the "mainpage.idx" file, which lists the files to include to generate it, instead of using the previous page-footer/headers. Also, those files are now also .md ones, using the same format. I gave them underscore prefixes to make them sort separately: _NAME.md, _SYNOPSIS.md, _DESCRIPTION.md, _URL.md, _GLOBBING.md, _VARIABLES.md, _OUTPUT.md, _PROTOCOLS.md, _PROGRESS.md, _VERSION.md, _OPTIONS.md, _FILES.md, _ENVIRONMENT.md, _PROXYPREFIX.md, _EXITCODES.md, _BUGS.md, _AUTHORS.md, _WWW.md, _SEEALSO.md - updated test cases accordingly Closes #12751
35 lines
1.1 KiB
Markdown
35 lines
1.1 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: key
|
|
Arg: <key>
|
|
Protocols: TLS SSH
|
|
Help: Private key file name
|
|
Category: tls ssh
|
|
Added: 7.9.3
|
|
Multi: single
|
|
See-also:
|
|
- key-type
|
|
- cert
|
|
Example:
|
|
- --cert certificate --key here $URL
|
|
---
|
|
|
|
# `--key`
|
|
|
|
Private key file name. Allows you to provide your private key in this separate
|
|
file. For SSH, if not specified, curl tries the following candidates in order:
|
|
`~/.ssh/id_rsa`, `~/.ssh/id_dsa`, `./id_rsa`, `./id_dsa`.
|
|
|
|
If curl is built against OpenSSL library, and the engine pkcs11 is available,
|
|
then a PKCS#11 URI (RFC 7512) can be used to specify a 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` if
|
|
none was provided.
|
|
|
|
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.
|