aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2000-06-05 08:21:28 +0000
committerDaniel Stenberg <daniel@haxx.se>2000-06-05 08:21:28 +0000
commit28b0b7316ddd0cc370f1e503066bb71f8fcb9b61 (patch)
treef65c4090e25e1827c8eb3a0695d127c6b831c3c4 /docs
parent57623228d21496783398c88dc712ffce4d8da305 (diff)
Added text about how to convert certificates to PEM format
Diffstat (limited to 'docs')
-rw-r--r--docs/README.curl20
1 files changed, 20 insertions, 0 deletions
diff --git a/docs/README.curl b/docs/README.curl
index ce2cba1d1..805c88d69 100644
--- a/docs/README.curl
+++ b/docs/README.curl
@@ -534,6 +534,26 @@ HTTPS
Otherwise, curl will first attempt to use v3 and then v2.
+ To use OpenSSL to convert your favourite browser's certificate into a PEM
+ formatted one that curl can use, do something like this (assuming netscape,
+ but IE is likely to work similarly):
+
+ You start with hitting the 'security' menu button in netscape.
+
+ Select 'certificates->yours' and then pick a certificate in the list
+
+ Press the 'export' button
+
+ enter your PIN code for the certs
+
+ select a proper place to save it
+
+ Run the 'openssl' application to convert the certificate. If you cd to the
+ openssl installation, you can do it like:
+
+ # ./apps/openssl pkcs12 -certfile [file you saved] -out [PEMfile]
+
+
RESUMING FILE TRANSFERS
To continue a file transfer where it was previously aborted, curl supports