[angry_octet]

Sorry but this is simply delusional. We're in an era where creds can be bought in online markets, and redis open source has no default requirement for password complexity.

If you can 'shit out endless bugs like this with AFL' then maybe redis isn't fit for purpose. But I think it more likely that it just needs hardening and an end to these laissez faire attitudes.

[illliillll]

Maybe share with us one good reason to not treat redis credentials like SSH credentials?

> and redis open source has no default requirement for password complexity.

Loudly Crying Face Emoji

[angry_octet]

You mean, like uncontrolled keys that can be used from anywhere and have no lifecycle care? Well at least SSH keys can't be guessed.

Redis suffers from security gatekeeping, where essential features are kept in the paid Enterprise fork, and community security efforts are blocked. So you can use x.509 mutual TLS certificate auth, but the setup is entirely manual. Which means you use long lived certificates, which is worse than hard passwords.

It needs short lived certificates and pinning against endpoints, and logging of endpoints against queries, and logging auth events/origins to the SIEM. If you have that setup then post-auth compromise is more manageable.

[inigyou]

Here's a thought: if you want something to exist, create it instead of begging a for-profit company to let you use their work for free.

[angry_octet]

Maybe for-profit companies shouldn't be gatekeeping core security features in open source products, and should instead deliver value in terms of debugging and performance, that are highly valued by enterprise customers.