4 ms·
Is there any reason I don’t just stick with redis 7.2.4 instead of trusting redict/valkey to not inject some backdoor trash? I can avoid the corporate pivot and
by hipadev23 3y ago
Is there any reason I don’t just stick with redis 7.2.4 instead of trusting redict/valkey to not inject some backdoor trash? I can avoid the corporate pivot and the random fork at the same time.
- wmf 3y agoOne is maintained and the other isn't. If you don't care about that you could definitely stick with the old version.
- hipadev23 3y agoRedis hasn’t materially changed since about 2.8 so tbh unmaintained is more than fine.
- kube-system 3y agoThis (and simliar) is pretty materially a good reason to update to something more modern: https://github.com/vulhub/vulhub/tree/master/redis/CVE-2022-0543 https://github.com/vulhub/vulhub/tree/master/redis/CVE-2022-...
- mrd3v0 3y agoThis new narrative makes it as if backdoors started existing the moment xz happened. As if that wasn't always a threat, and that xz more than anything did prove that free software is a lot more resilient than to suffer similar attacks that have happened and will continue to happen without public acknowlegement or as much publicity in unfree software/SaaS.
- justinclift 3y agoMaybe take a look at the other fork, Redict? https://redict.io https://redict.io
- deleted 3y ago[deleted]