Password Generator

passwordgen.org

4.7(

12 ratings

)

ExtensionWorkflow & Planning337 users

4 support issues

Andrius Žilėnas

Sep 9, 2016

backslash as escape instead symbol

recently I had problem when 'insert' skipped backslash i.e. inserted:
(!
- different password than 'copy':
(\!

Aarian P. Aleahmad

Jan 18, 2015

Hashing Algorithms

It would be great if your application could use newer and better hashing algorithms (Including SHA3 Family)

Jonathan Chen

May 21, 2014

Handling of non-US domains - .nz

Your exception list will get bigger, as I'm experiencing the same issue, but for .nz based domains. eg: .co.nz, .net.nz, .org.nz, etc

I would suggest that if the last component is a 2-letters in length, ie: a country-level TLD, it will default to using 3 components instead.

Unfortunately, some non-US domains only use 2 components as well. The only long term solution I can see is to include the number of components in the "Profile"; ie all non-US, 3 component domains can be lumped together in one profile.

Oleg Eterevsky

Developer

Jun 7, 2014

I've just published a new version that should correctly handle all the top-level domains. If you notice any more problems with TLD recognition, please post another report here or at on GitHub: https://github.com/eterevsky/passwordgen/issues

Tim McBlonderson

Nov 7, 2013

Handling of non-US domains

Hi!

Currently the password generator doesn't seem to deal with .com.au very well - the generated domain name for all Australian websites is just ".com.au". Furthermore, it can't remember that it has been overrridden for a particular website, so I have to reenter my choice every time!

Is it possible that the default number of domain components to use could increase to 3 if the last component is a country-level TLD?

e.g. ending in .uk or .au, it should include three components rather than 2 in the default?

Thanks,
Tim

Oleg Eterevsky

Developer

Dec 9, 2013

Hi! Thanks for your feedback. I uploaded a new version fixing this bug.

Switching from 2nd level domain to 3rd level won't work, since it will produce different passwords for, say, google.com and www.google.com, which is obviously not what users want. To deal with it, I just added a least for effectively top-level domains, but failed to add com.au to it. Now it's fixed.

P.S. It's a pity I don't get email notifications about WebStore feedback, otherwise, I would have fixed it right away.