Re: Handling elements of an array of array references, where the function calls for an array?

Hi desertrat,
before I spend time on working out how to do it, I'd rather spend a few minutes persuading you that it's not a good idea. I know, oftentimes it's come corporate-level decision that you just have to implement, but if you have any say in it: don't. It's fine to require some classes of characters to keep people from using all too simple variations of distionary words, but

four is excessive, i.e. it already limits the number of allowable passwords too much, and
imposing rules on supposedly "random" distribution limits them even more, making brute-force cracking actually easier.

I'd suggest using Crypt::Cracklib or somesuch password checker on generated results and retrying if it finds the result all too easily crackable.

Comment on Re: Handling elements of an array of array references, where the function calls for an array?

Replies are listed 'Best First'.
Re^2: Handling elements of an array of array references, where the function calls for an array? by desertrat (Sexton) on May 14, 2012 at 21:41 UTC
Sadly it's a corporate-level decision being made by an entirely different corporation (We have a group contracted to do work for outside companies), so I have to do it this way. I know this is a PITA and just results in passwords being taped to the front of monitors, let alone under the keyboards, but a code monkey's gotta do what a code monkey's gotta do sometimes. Had I any say I would offer Randall Munroe's excellent treatise on the matter as the help file.	[reply]

Replies are listed 'Best First'.

Re^2: Handling elements of an array of array references, where the function calls for an array?
by desertrat (Sexton) on May 14, 2012 at 21:41 UTC

Sadly it's a corporate-level decision being made by an entirely different corporation (We have a group contracted to do work for outside companies), so I have to do it this way. I know this is a PITA and just results in passwords being taped to the front of monitors, let alone under the keyboards, but a code monkey's gotta do what a code monkey's gotta do sometimes.

Had I any say I would offer Randall Munroe's excellent treatise on the matter as the help file.

[reply]