4 ms·
According to the article the security flaw was just that the DB was not secured with any password. There could be a legitimate reason for that and it's not a fl
by superfrank 7y ago
According to the article the security flaw was just that the DB was not secured with any password. There could be a legitimate reason for that and it's not a flaw in the technology, so it's really not something AWS should be doing something about (other than maybe reaching out to the user to confirm that the lack of password is intended).
Honestly, I would be a little worried if AWS saw that a user had a DB with no password and decided to either add a password or block access to the DB without the user's consent.
- jedberg 7y agoI wouldn't expect AWS to do anything like that. I'd expect AWS to understand the implication of a database of private data being publicly accessible and having the account rep reach out to the owner and let them know.