Repositories held for ransom by using valid credentials

Re:Repositories held for ransom by using valid credentials by tjr225 on Saturday May 04, 2019 @03:32PM (#19828708)

I had accidentally pushed an AWS credential out a month or two ago- within about a minute and a half AWS had disabled the IAM user, and automatically emailed me(as well as my entire org- how embarrassing!)- when we were going through the access logs it looked like it had taken only a minute and a half longer for some other, presumably malicious, system to attempt to access my compromised user. Probably between 2 or 3 minutes total. I'm not a huge Amazon fan but props to AWS for saving my butt.

[ Parent | on HN ]

Re:Repositories held for ransom by using valid credentials by scarface74 on Saturday May 04, 2019 @05:58PM (#19829644)

Why have credentials anywhere outside of the .aws directory in your home directory? When developing locally all of the SDKs will read them from there and when deploying to AWS, the SDK will get them from the attached role.

[ Parent | on HN ]

Re:Repositories held for ransom by using valid credentials by tjr225 on Saturday May 04, 2019 @06:38PM (#19829836)

I understand what the best practices are, it was a total mistake- I never even intended to push what I did to github.

[ Parent | on HN ]

Re:Repositories held for ransom by using valid credentials by house9-2 on Tuesday May 07, 2019 @12:40AM (#19846647)

`git diff` before making a commit `git log` and `git show` before pushing to a remote

These 2 simple things have saved me on more than one occasion.

[ Parent | on HN ]