diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-08-28 12:20:01 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2015-09-03 10:59:19 +0200 |
| commit | 57d85d9bee20edb6c3070504f23b6a2be2802654 (patch) | |
| tree | b08ba54e5e74d3353a717feada510b4fb97bbf27 | |
| parent | 40b556d3742a1f65d67e2d4c760d0b13fe8be5b7 (diff) | |
doc: mention SSL support dropped for RPC in release notes
| -rw-r--r-- | doc/release-notes.md | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 9caac4f7ae..2fc601d435 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -4,6 +4,29 @@ release-notes at release time) Notable changes =============== +SSL support for RPC dropped +---------------------------- + +SSL support for RPC, previously enabled by the option `rpcssl` has been dropped +from both the client and the server. This was done in preparation for removing +the dependency on OpenSSL for the daemon completely. + +Trying to use `rpcssl` will result in an error: + + Error: SSL mode for RPC (-rpcssl) is no longer supported. + +If you are one of the few people that relies on this feature, a flexible +migration path is to use `stunnel`. This is an utility that can tunnel +arbitrary TCP connections inside SSL. On e.g. Ubuntu it can be installed with: + + sudo apt-get install stunnel4 + +Then, to tunnel a SSL connection on 28332 to a RPC server bound on localhost on port 18332 do: + + stunnel -d 28332 -r 127.0.0.1:18332 -p stunnel.pem -P '' + +It can also be set up system-wide in inetd style. + Random-cookie RPC authentication --------------------------------- |