Github Kills Search After Hundreds of Private Keys Exposed 176
mask.of.sanity writes "Github has killed its search function to safeguard users who were caught out storing keys and passwords in public repositories. 'Users found that quite a large number of users who had added private keys to their repositories and then pushed the files up to GitHub. Searching on id_rsa, a file which contains the private key for SSH logins, returned over 600 results. Projects had live configuration files from cloud services such as Amazon Web Services and Azure with the encryption keys still included. Configuration and private key files are intended to be kept secret, since if it falls into wrong hands, that person can impersonate the user (or at least, the user's machine) and easily connect to that remote machine.' Search links popped up throughout Twitter pointing to stored keys, including what was reportedly account credentials for the Google Chrome source code repository. The keys can still be found using search engines, so check your repos."
At least... (Score:5, Funny)
they've been seen by 'many eye balls'.
That's good right?
Re:Search engines (Score:5, Funny)
Stop, Google will shutdown search because of that
Re:At least... (Score:5, Funny)
Nothing has changed... (Score:5, Funny)
Looks like these grad students have all growned up and uploading it all to the cloud.
Re:Nothing has changed... (Score:5, Funny)
Yeah ... I was "that guy". The first time I installed Linux in 2000, I was annoyed that I needed "permission" to write to a directory outside of my home directory. I was coming from a Windows world, after all.
I solved this "problem" by chmod 777 the entire filesystem. Hah. Problem solved. Needless to say, I couldn't start the machine back up again. I'm guessing it killed itself from the shear embarrassment. After that, I decided it may be in my best interest to read the manual.
I'll do that one of these days :)