Closed GoogleCodeExporter closed 8 years ago
Thanks Sean!
I'll have to give some thought as to whether PasswordGenerator should be an
interface
that rules implement.
It also seems like you would want to consolidate generation over several rules,
but
on the surface that appears to be very difficult.
Great stuff, I'll try to get this merged in the next month or so.
Original comment by dfis...@gmail.com
on 16 Nov 2009 at 3:36
Original comment by dfis...@gmail.com
on 30 Jan 2010 at 7:42
Committed in r1115.
Added constructor that accepts non-alphanumeric characters, as that seems like a
field that users might want to customize.
Modified the code the fills out the password length to use all available
characters.
Check out the latest snapshot and let me know what you think.
Original comment by dfis...@gmail.com
on 1 Feb 2010 at 5:12
Attached patch to avoid Collections.shuffle and duplication of character data.
Original comment by marvin.addison@gmail.com
on 1 Feb 2010 at 8:59
Attachments:
Just noticed I had inadvertently truncated a Javadoc comment on previous diff.
Corrected patch is attached.
Original comment by marvin.addison@gmail.com
on 1 Feb 2010 at 9:09
Attachments:
Applied your patch in r1125.
Also removed the final declaration and made the fields protected for
overloading.
Did you run any tests to confirm your patch is more performant than
Collections.shuffle()?
Original comment by dfis...@gmail.com
on 1 Feb 2010 at 9:30
vt-password 2.0.2 tagged.
Original comment by dfis...@gmail.com
on 20 Apr 2010 at 4:12
Original issue reported on code.google.com by
sean%sea...@gtempaccount.com
on 12 Nov 2009 at 5:24Attachments: