Re:A Docker footgun led to a vandal deleting NewsBlur's Mong...
by QuinnyPig on Sunday February 19, 2023 @02:18PM
(#34860822)
They becomes a highly effective denial of service vector if you’re not careful.
Re:A Docker footgun led to a vandal deleting NewsBlur's Mong...
by bastawhiz on Sunday February 19, 2023 @02:44PM
(#34861083)
> if you’re not careful.
I don't think there's a way to avoid a DOS vector even if you're careful. If someone can access your database directly, they can make enough attempts to lock a user. The only way to be careful is to avoid public access to the db. But if you do that effectively, you don't have the issue of accounts getting locked.
It's a dubious argument to ever lock an account as a safety measure. Arguably, downtime is not a good tradeoff, especially if you're following best practices and using a very long, truly random password. An extremely secure db setup shouldn't require you to disable a "safety" feature that creates a new DoS vector because you've followed best practices.
Re:A Docker footgun led to a vandal deleting NewsBlur's Mong...
by throwaway744678 on Sunday February 19, 2023 @03:43PM
(#34861669)
Fail2ban is a good mitigation strategy, blocking the IP address after N failed attempts (obviously, it does not protect completely from a determined attacker controlling a network of bots but it raises the bar significantly)
Re:A Docker footgun led to a vandal deleting NewsBlur's Mong...
by SahAssar on Sunday February 19, 2023 @03:46PM
(#34861705)
How does locking a account after failed attempts to access it make sense? By failing to access the account I have proved nothing besides that I know a username (which is usually not secret).
Neither do other databases like PG, curiously enough. The recommendation seems to be to link to LDAP or use authentication hooks.
Or perhaps use client and server certificates for increased security - https://www.postgresql.org/docs/current/ssl-tcp.html#SSL-SER...