3 ms·
But what if your codebase is used in thousands of places that you don't control? You can't always change it. The real lesson is - don't put passwords in your c
by olegkikin 10y ago
But what if your codebase is used in thousands of places that you don't control? You can't always change it.
The real lesson is - don't put passwords in your code.
- vbezhenar 10y agoUsing the same password in thounsands of places isn't good either. Use unique random passwords.
- tetrep 10y agoDon't use passwords/secrets/credentials that you can't rotate. If you've created a product in such a way that you can't rotate secrets, you have a large security issue that you should fix ASAP. It's like someone responding to the suggestion to "use strong/unique passwords" with "but what if I don't have any authentication?"