A security auditor for our servers has demanded the following within two weeks:
- A list of current usernames and plain-text passwords for all user accounts on all servers
- A list of all password changes for the past six months, again in plain-text
- A list of "every file added to the server from remote devices" in the past six months
- The public and private keys of any SSH keys
- An email sent to him every time a user changes their password, containing the plain text password
I forget where, but I found this app online that would estimate how long it'd take to brute-force your password. I don't know what the brute-force or hashing algorithms it assumed were, but it estimated something like 17 trillion years for most of my passwords...– Jul 29 '11 at 5:11
10
the online app I found to estimate password strength had a different (and possibly more accurate) approach: for every password, it returned "Your password is insecure - you just typed it into an untrusted web page!" – Jul 29 '11 at 5:49
oh no, you're right! – Jul 29 '11 at 6:03
roddierod said:I'm not sure if the security auditor is a idiot or a genius in this case, but from my experience I'm going to have to go with the 1st choice.
graudeejs said:https://github.com/rails/rails/issues?sort=created&direction=desc&state=closed
Check date of first closed issue in the list and read the PR
Article on h-online
http://www.h-online.com/open/news/i...highlights-Ruby-on-Rails-problem-1463207.html
A security vulnerability was recently discovered that made it possible for an attacker to add new SSH keys to arbitrary GitHub user accounts. This would have provided an attacker with clone/pull access to repositories with read permissions, and clone/pull/push access to repositories with write permissions. As of 5:53 PM UTC on Sunday, March 4th the vulnerability no longer exists.
While no known malicious activity has been reported, we are taking additional precautions by forcing an audit of all existing SSH keys.
# Required Action
Since you have one or more SSH keys associated with your GitHub account you must visit https://github.com/settings/ssh/audit to approve each valid SSH key.
Until you have approved your SSH keys, you will be unable to clone/pull/push your repositories over SSH.
# Status
We take security seriously and recognize this never should have happened. In addition to a full code audit, we have taken the following measures to enhance the security of your account:
- We are forcing an audit of all existing SSH keys
- Adding a new SSH key will now prompt for your password
- We will now email you any time a new SSH key is added to your account
- You now have access to a log of account changes in your Account Settings page
Sincerely, The GitHub Team
matoatlantis said:And you would wonder how many users worldwide have 'Monday01' as a password.
peetaur said:Code:SELECT count(*) c, password FROM user GROUP BY password ORDER BY password HAVING c>1
matoatlantis said:So what was the biggest 'c' on big production DB ?
sossego said:I named my kitten Schrödinger.
athos said:Is he alive? XD
saxon3049 said:Asking that question collapsed the field and made the kitten implode, Feel good about what you have just done? You just made a kitten implode.
I thought it was poisonedsaxon3049 said:Asking that question collapsed the field and made the kitten implode
ring_zero said:Over zealous autoconfig:
http://xkcd.com/416/
And this one too
http://xkcd.com/421/
And this one
http://xkcd.com/421/