Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • the reason is to guarantee the uniqueness of each password, nut just by possibility (62^32) but by storing and checking each generated password against this database. we had a security-audit (with even more silly recommendations ... ) and our bosses believe those powerpoint-presentations more than our experience. we even showed a calculation on how many thousends of years are needed to generate a password twice, even if we generate 100 password/second, 24/7, sic Commented Sep 6, 2013 at 9:41
  • @castorio So ask yourself why is it important to guarantee uniqueness? But sure, if it's unavoidable just do it. Like I mentioned, there won't be a security drawback. Commented Sep 6, 2013 at 9:55
  • @castorio Still, maybe you can convince your bosses by telling them how much additional resources this requirement will need (hard disk space, processing power to hash and compare every time a random password is generated...). Commented Sep 6, 2013 at 9:56
  • terry, i'm on your site here, thanx for your suggestions. btw, resources are not the problem. Commented Sep 6, 2013 at 11:54