diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2004-06-30 11:34:57 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2004-06-30 11:34:57 +0000 |
| commit | c14650caec03669b80324854c0a70dcc5301e59c (patch) | |
| tree | 7bd4338a0cfa458fc358b56ee1813d8831928c8d /docs/TheArtOfHttpScripting | |
| parent | c7a9e07909484c30707bcae70d5eae3e44d91b71 (diff) | |
not PIN code, pass phrase
Diffstat (limited to 'docs/TheArtOfHttpScripting')
| -rw-r--r-- | docs/TheArtOfHttpScripting | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/TheArtOfHttpScripting b/docs/TheArtOfHttpScripting index 1499df0ea..01ece3c54 100644 --- a/docs/TheArtOfHttpScripting +++ b/docs/TheArtOfHttpScripting @@ -370,11 +370,11 @@ Version: 0.6 In the HTTPS world, you use certificates to validate that you are the one you you claim to be, as an addition to normal passwords. Curl supports - client-side certificates. All certificates are locked with a PIN-code, why - you need to enter the unlock-code before the certificate can be used by - curl. The PIN-code can be specified on the command line or if not, entered - interactively when curl queries for it. Use a certificate with curl on a - HTTPS server like: + client-side certificates. All certificates are locked with a pass phrase, + which you need to enter before the certificate can be used by curl. The pass + phrase can be specified on the command line or if not, entered interactively + when curl queries for it. Use a certificate with curl on a HTTPS server + like: curl -E mycert.pem https://that.secure.server.com |