9 ms·
Either a dev was playing around and oopsied or they got hacked.
by wjd2030 7y ago
Either a dev was playing around and oopsied or they got hacked.
- willis936 7y agoAlmost certainly the former. Careful people need to be in charge and keep a tight leash on people who are careless until they are careful. Also pre-emptive response to “something something about systems something cgpgrey”. At the end of the day we live in the real world with imperfections everywhere. Every system eventually boils down to trust in humans.
- z3t4 7y ago1 (number one) is popular in "injection" attacks as it is likely to go through and not throw an error. If you login as admin to your web based control panel and is greeted with an alert(1) you know you are fucked.
- INTPenis 7y agoI've never been a dev in such a large environment but devs shouldn't even be able to touch such a production environment imo. They do their testing and then hand over to deployment. After that they're out of the picture until the next update needs to roll out. They can't have direct access to API keys for live apps in production.
- thecatspaw 7y agoand this is the reason why all my tests are reasonable sane strings which customers could see and not something like "fuck 1", "fuck 2", etc
- RL_Quine 7y agoOn the other hand I'd say that having them be that is more incentive to keep things safe.