|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Today @ 12:44 PM
Points: 802,
Visits: 2,012
|
|
Comments posted to this topic are about the item Generate a random password
Gaby ________________________________________________________________ "In theory, theory and practice are the same. In practice, they are not." - Albert Einstein
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Thursday, June 06, 2013 6:31 AM
Points: 438,
Visits: 919
|
|
Nice !
There also might be confusion between letter "G" and number 6...
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Monday, June 03, 2013 8:15 AM
Points: 1,508,
Visits: 620
|
|
| The password generator does a nice job, but while testing the code in QA, I noted that the proc does seem to return an "abundant" number of 'repeats' in any given password. In some generated passwords, I count up to three pairs of the same letters or characters. Can this be considered acceptable for 10 character passwords?
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Thursday, June 06, 2013 6:31 AM
Points: 438,
Visits: 919
|
|
woops...
I did not try to run and test the code.
Thanks for doing this. Very useful.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 5:43 PM
Points: 298,
Visits: 1,320
|
|
Works great and I actually needed something like this today! Thanks!
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 5:19 PM
Points: 33,110,
Visits: 27,035
|
|
Pretty nice, Gaby... your article and some of the comments above gave me a couple of ideas for an article with just a pot-wad of tricks in it... Ok if I reference your article?
--Jeff Moden "RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."
For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Today @ 5:43 PM
Points: 298,
Visits: 1,320
|
|
One additional thing I'd like to see is the ability to force at least one number and/or one special character.
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Today @ 9:46 AM
Points: 1,269,
Visits: 1,492
|
|
No knock on the script, but I question the value of truly random passwords.
I think I have a pretty good memory. I have my credit card number memorized (okay - maybe that's a bad thing ). For passwords I think there should be some sensible pattern.
I tend to build passwords (at least 9 char) using the user's initials mixed-up, or a misspelling of their name with odd capitalization. I usually include part of they phone number, and/or birth date, and I always include a special character or two. The point is that it's something that forms a memorable pattern to the user. I think I can do this and still maintain a high level of security.
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Thursday, June 06, 2013 6:31 AM
Points: 438,
Visits: 919
|
|
RML51:
Unless you will not allow the users to change their password to one of their own liking -- for instance banks DO allow users to change their PIN number and others do supply a password intended to be changed by the user, then I do not see the point in enforcing a pattern to help the users to remember their password.
If you were to allow users to change password, you could implement instead a password validation routine that would filter out the most commonly used passwords such as "Rolex", "guest", "admin", "sysadmin"" etc. Specify a minimum length, force the use of special characters like !, $, {, }, etc. and a non -zero count of upper and lower case alphabetic characters.
You could also set a maximum length and ban the use of the : character. Would help (no guarantees) reject injection attacks and scripts if you have poorly written applications.
The pattern enforcement scheme would be intended at rejecting non compliant user-entered passwords instead of helping users to remember a password.
And even if you did supply a pattern, if it contains random characters, this would not help the users. Some of them out there really have a hard time with spotting patterns. If they can't remember a password, I would not bank too much on them remembering a pattern either.
|
|
|
|
|
SSC Eights!
      
Group: General Forum Members
Last Login: Today @ 12:44 PM
Points: 802,
Visits: 2,012
|
|
Jeff Moden (11/13/2008) Pretty nice, Gaby... your article and some of the comments above gave me a couple of ideas for an article with just a pot-wad of tricks in it... Ok if I reference your article?
Hey Jeff, sorry about the delayed response. Please feel free to use this.
Gaby ________________________________________________________________ "In theory, theory and practice are the same. In practice, they are not." - Albert Einstein
|
|
|
|