171–180 of 266 posts
Earlier quoted context omitted.
Yeah, I just started getting those too. But adding "&p=2" to the URL shows results for the next page... shrug
You could probably also just use Google to find them with site:github.com.
(No, I didn't exploit this, I just enjoyed finding them)
Earlier quoted context omitted.
I should be amazed at how prevalent this is but after almost two decades in IT/IS, it's no more than the equivalent to the Post-IT on a monitor, but more accessible. Dumb, but business as usual.
> the equivalent to the Post-IT on a monitor Writing passwords down on a piece of paper, and keeping that in your wallet or locked desk drawer is actually one of the more secure ways of storing passwords these days. No risk of electronic compromise, and its highly unlikely that people who would steal your wallet or break into your home are also interested in your online accounts.
Earlier quoted context omitted.
I should be amazed at how prevalent this is but after almost two decades in IT/IS, it's no more than the equivalent to the Post-IT on a monitor, but more accessible. Dumb, but business as usual.
> the equivalent to the Post-IT on a monitor Writing passwords down on a piece of paper, and keeping that in your wallet or locked desk drawer is actually one of the more secure ways of storing passwords these days. No risk of electronic compromise, and its highly unlikely that people who would steal your wallet or break into your home are also interested in your online accounts.
Earlier quoted context omitted.
I should be amazed at how prevalent this is but after almost two decades in IT/IS, it's no more than the equivalent to the Post-IT on a monitor, but more accessible. Dumb, but business as usual.
> the equivalent to the Post-IT on a monitor Writing passwords down on a piece of paper, and keeping that in your wallet or locked desk drawer is actually one of the more secure ways of storing passwords these days. No risk of electronic compromise, and its highly unlikely that people who would steal your wallet or break into your home are also interested in your online accounts.
1. New guy gets hired.
2.You work for a large corporation and we'll you can't say you can trust everyone there.
3. Small company of 10 (company I work at for example) could be compromised by the weekly janitor.
4. Someone could break in and make it look like a robbery all while stealing your critical infrastructure.
I recently helped research a bit about internal security for our office and sticky notes are still a very common place for credentials to be compromised.
Too many comments here recommend to clean up the commit and just hide the mistake under the rug. This is wrong. If you leak a password to any public location, there is only one reasonable course of action: CHANGE IT! Don't even bother rewriting the commit. Focus on changing that password right away, and while you're at it, figure out a better way to manage your secrets outside of your source code in the future. Mista…
the solution is to store the password and any other sensitive information in a text file that you read when your program starts up. And don't forget to add that file's name to .gitignore so git will ignore it. As simple as that. :) If you leaked the password in the git repository, change it as @jvehent just commented.
This could be a big thing. It's time to write: How to write code without expose you
Even more frightening: https://github.com/search?utf8=&q=id_rsa&type=Commits&ref=se...
Even more frightening: https://github.com/search?utf8=&q=id_rsa&type=Commits&ref=se...