From a9793819fee53880751610dc355927ee8f7f213b Mon Sep 17 00:00:00 2001 From: Roman Reiss Date: Wed, 18 Feb 2015 17:55:11 +0100 Subject: [PATCH] doc: document 'ciphers' option of tls.connect This option has been there for a long time, but has never been documented. It's functionally identical to the server counterpart. --- doc/api/tls.markdown | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/api/tls.markdown b/doc/api/tls.markdown index c5cfc1562ad028..1b850570d06822 100644 --- a/doc/api/tls.markdown +++ b/doc/api/tls.markdown @@ -314,6 +314,9 @@ Creates a new client connection to the given `port` and `host` (old API) or format. If this is omitted several well known "root" CAs will be used, like VeriSign. These are used to authorize connections. + - `ciphers`: A string describing the ciphers to use or exclude, separated by + `:`. Uses the same default cipher suite as `tls.createServer`. + - `rejectUnauthorized`: If `true`, the server certificate is verified against the list of supplied CAs. An `'error'` event is emitted if verification fails; `err.code` contains the OpenSSL error code. Default: `true`.