Download-Tools/aria2
1
0
Fork 0
mirror of https://github.com/aria2/aria2.git synced 2025-01-08 11:01:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Document WinTLS, AppleTLS, PKCS12 for --certificate

Browse Source
This commit is contained in:
Nils Maier 2013-09-30 16:49:10 +02:00
parent 3b35887827
commit 41bee45792
1 changed files with 31 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
doc/manual-src/en/aria2c.rst
View File

@ -349,9 +349,26 @@ HTTP Specific Options
.. option:: --certificate=<FILE>
Use the client certificate in FILE.
The certificate must be in PEM format.
You may use :option:`--private-key` option to specify the private key.
Use the client certificate in FILE. The certificate must be
either in PKCS12 (.p12, .pfx) or in PEM format.
PKCS12 files must contain the certificate, a key and optionally a chain
of additional certificates. Only PKCS12 files with a blank import password
can be opened!
When using PEM, you have to specify the private key via :option:`--private-key`
as well.
.. note::
*WinTLS* does not support PEM files at the moment. Users have to use PKCS12
files.
.. note::
*AppleTLS* users should use the Keychain Access utility to import the client
certificate and get the SHA-1 fingerprint from the Information dialog
corresponding to that certificate.
To start aria2c use `--certificate=<SHA-1>` and just omit the
:option:`--private-key` option.
.. option:: --check-certificate[=true|false]
@ -931,15 +948,18 @@ RPC Options
When using PEM, you have to specify the private key via :option:`--rpc-private-key`
as well. Use :option:`--rpc-secure` option to enable encryption.
*WinTLS* does not support PEM files at the moment. Users have to use PKCS12 files.
.. note::
*WinTLS* does not support PEM files at the moment. Users have to use PKCS12
files.
*AppleTLS* users should use the Keychain Access utility to first generate a
self-signed SSL-Server certificate, e.g. using the wizard, and get the
SHA-1 fingerprint from the Information dialog corresponding to that new
certificate.
To start aria2c with :option:`--rpc-secure` use
`--rpc-certificate=<SHA-1>` and just omit the :option:`--rpc-private-key`
option.
.. note::
*AppleTLS* users should use the Keychain Access utility to first generate a
self-signed SSL-Server certificate, e.g. using the wizard, and get the
SHA-1 fingerprint from the Information dialog corresponding to that new
certificate.
To start aria2c with :option:`--rpc-secure` use
`--rpc-certificate=<SHA-1>` and just omit the :option:`--rpc-private-key`
option.
.. option:: --rpc-listen-all[=true|false]