You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
At first, You're right! It saves us from memory attack, core dump, etc.
We need to change method signature, and it means we should break compatibility.
So we can schedule it to major release (currently 3.0.0).
We would very happy with you providing pull request!
Btw, Redis is not designed to strong security. Please refer http://redis.io/topics/security for details.
Especially AUTH command sent to Redis unencrypted, so Redis is exposed to network attacker!
So you should use firewall, or add security layers (ex. SSL) before use Redis.
Only using password never saves us.
References:
1. #1602 and related PRs. Current PR is probably better than handling in JedisFactory
2. redis/redis-py#2261 - main reason of this PR
3. redis/lettuce#1774
4. #632
---
* Introduce credentials provider
* use volatile
* Test in Sentineled mode
* Support CharSequence in DefaultRedisCredentials
* Added doc for prepare() and cleanUp()
* Test the provider interface
* Added example
* Removed deprecations
Jedis stores Redis server password as a String. Both "Java Cryptography Architecture guide" and "Secure Coding Guidelines for Java SE" recommend that sensitive information be stored in char array instead of a String.
The text was updated successfully, but these errors were encountered: