fluencelabs/redis
1
0
Fork 0
mirror of https://github.com/fluencelabs/redis synced 2025-04-25 10:32:14 +00:00
Code Issues Projects Releases Wiki Activity

TLS: Update documentation.

Browse Source
This commit is contained in:
Yossi Gottlieb 2020-02-05 21:13:21 +02:00 committed by antirez
parent 4440133e9a
commit 9baaf858f9
2 changed files with 32 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -35,6 +35,11 @@ It is as simple as:
% make % make
To build with TLS support, you'll need OpenSSL development libraries (e.g.
libssl-dev on Debian/Ubuntu) and run:
% make BUILD_TLS=yes
You can run a 32 bit Redis binary using: You can run a 32 bit Redis binary using:
% make 32bit % make 32bit
@ -43,6 +48,13 @@ After building Redis, it is a good idea to test it using:
% make test % make test
If TLS is built, running the tests with TLS enabled (you will need `tcl-tls`
installed):
% ./utils/gen-test-certs.sh
% ./runtest --tls
Fixing build problems with dependencies or cached build options Fixing build problems with dependencies or cached build options
--------- ---------
@ -125,6 +137,12 @@ as options using the command line. Examples:
All the options in redis.conf are also supported as options using the command All the options in redis.conf are also supported as options using the command
line, with exactly the same name. line, with exactly the same name.
Running Redis with TLS:
------------------
Please consult the [TLS.md](TLS.md) file for more information on
how to use Redis with TLS.
Playing with Redis Playing with Redis
------------------ ------------------

45
TLS.md
View File

@ -1,8 +1,5 @@
TLS Support -- Work In Progress TLS Support
=============================== ===========
This is a brief note to capture current thoughts/ideas and track pending action
items.
Getting Started Getting Started
--------------- ---------------
@ -69,37 +66,23 @@ probably not be so hard. For cluster keys migration it might be more difficult,
but there are probably other good reasons to improve that part anyway. but there are probably other good reasons to improve that part anyway.
To-Do List To-Do List
========== ----------
Additional TLS Features - [ ] Add session caching support. Check if/how it's handled by clients to
----------------------- assess how useful/important it is.
- [ ] redis-benchmark support. The current implementation is a mix of using
hiredis for parsing and basic networking (establishing connections), but
directly manipulating sockets for most actions. This will need to be cleaned
up for proper TLS support. The best approach is probably to migrate to hiredis
async mode.
- [ ] redis-cli `--slave` and `--rdb` support.
1. Add metrics to INFO? Multi-port
2. Add session caching support. Check if/how it's handled by clients to assess ----------
how useful/important it is.
redis-benchmark
---------------
The current implementation is a mix of using hiredis for parsing and basic
networking (establishing connections), but directly manipulating sockets for
most actions.
This will need to be cleaned up for proper TLS support. The best approach is
probably to migrate to hiredis async mode.
redis-cli
---------
1. Add support for TLS in --slave and --rdb modes.
Others
------
Consider the implications of allowing TLS to be configured on a separate port, Consider the implications of allowing TLS to be configured on a separate port,
making Redis listening on multiple ports. making Redis listening on multiple ports:
This impacts many things, like
1. Startup banner port notification 1. Startup banner port notification
2. Proctitle 2. Proctitle
3. How slaves announce themselves 3. How slaves announce themselves