Description: Password Creator is a great tool to generate passwords with criteria like uppercase letters, numbers or even specified characters.
It has virtually no limitation on the pasword length and the password quantity or the characters to use.
/! Please reptort bugs or features at http://www.vilers.net/post.phpLast changelog:
1.1.2: released on 17 Oct 2004 ------------------------------ * Fixed the excellent rating bug when one character length. * Fixed pronoucable passwords to not start with two vowels.
1.1.1: released on 06 Oct 2004 ------------------------------ * Fixed the make install problem.
1.1: released on 05 Oct 2004 ---------------------------- * Added the password quality evaluation. * Added the pronoucable password. Must still be improved. * Added a menubar with File/Exit and Help/About. * Added a modest about box. * Added the specific exclude characters. * Added the '>' and '<' character to the default signs pool. * Added an automatic settings save on exit.
1.0.1: released on 03 Oct 2004 ------------------------------ * Added the the unistd.h include that is needed on some distributions.
1.0: released on 02 Oct 2004 ---------------------------- * Initial release.
Why the ^#(( did you embed the icons in the executable? Worse, why did you embed Crystal style icons.
KDE has standards for icons and they should be followed.
IAC, you need to supply icons for the menu entry.
I tired to install on my SuSE 9.1 Pro system. I followed the instructions in the Install file for the latest (10/6) version. Here is my output:
jsnyder@linux:~/Software/passwordcreator> qmake -o Makefile passwordcreator.pro
jsnyder@linux:~/Software/passwordcreator> make
cd src && make -f Makefile
make[1]: Entering directory `/home/jsnyder/Software/passwordcreator/src'
make[1]: *** No rule to make target `/usr/qt/3/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop.
make[1]: Leaving directory `/home/jsnyder/Software/passwordcreator/src'
make: *** [sub-src] Error 2
It seems that the Makefile is looking in the wrong place to find qmake.conf. On SuSE the qmake.conf file is located at:
/usr/lib/qt3/mkspecs/linux-g++/qmake.conf
How can I fix this problem to be able to run "make"? I looked in the /src/Makefile and manually reset the path, but still I get this error. Thanks.
On debian qt3 is not in /usr/qt/3/ but in /usr/qt3/ or well... it is on my half package half self compiled system.
Further, my qt is multithreaded and the makefile assumes -lqt where in my case it is -lqt-mt.
How about configure? :)
I created a similar script in php once that had 1 distinguished feature: all generated passwords were pronouncable.
In my experience users tend to stick to the initial passwords more often if they can pronounce it! Would be nice to add.
The algorithm for creating a readable password I came up with:
array C are Consonants
array V are Vowels
array A are C+V
1. Choose a random char from A
2. if (previous 2 chars were 2xC or 2xV) choose from 'the other side' else: 1.
3. if char is last char: never end with double V.
It's not foolproof, but a nice start.
Additionally you could replace all characters that look like numbers. e.g. i = 1, e=3, s=5, z=2 etc...
The script:
http://www.mrvanes.com/randpass.php
Hi Neptune,
Great little tool you have here. Had a little compilation problem. Had to include unistd.h in src/passwordcreator.cpp so that the call to getpid() worked..
Hmm, thanks for the information. I don't need this include on my machine, but i'll commit this change immediately. I'll try to find from wich include I got getpid() declaration.
Would it be possible to add sometinhg like
"How-Easy-To-Hack"-status. If you have
only numbers, it may be easier and then,
somewhere, there could be a bar or a text
"98.392 % safe" or something like that.
Hmm you understand? =/
Hmm, I understand perfectly ;-)
Nice idea, I'll put it on the TODO list.
Note that no password will never 100% safe. Too many people write them on post-it ;-)
Ratings & Comments
18 Comments
Why the ^#(( did you embed the icons in the executable? Worse, why did you embed Crystal style icons. KDE has standards for icons and they should be followed. IAC, you need to supply icons for the menu entry.
I tired to install on my SuSE 9.1 Pro system. I followed the instructions in the Install file for the latest (10/6) version. Here is my output: jsnyder@linux:~/Software/passwordcreator> qmake -o Makefile passwordcreator.pro jsnyder@linux:~/Software/passwordcreator> make cd src && make -f Makefile make[1]: Entering directory `/home/jsnyder/Software/passwordcreator/src' make[1]: *** No rule to make target `/usr/qt/3/mkspecs/linux-g++/qmake.conf', needed by `Makefile'. Stop. make[1]: Leaving directory `/home/jsnyder/Software/passwordcreator/src' make: *** [sub-src] Error 2 It seems that the Makefile is looking in the wrong place to find qmake.conf. On SuSE the qmake.conf file is located at: /usr/lib/qt3/mkspecs/linux-g++/qmake.conf How can I fix this problem to be able to run "make"? I looked in the /src/Makefile and manually reset the path, but still I get this error. Thanks.
hmm, strange, could you try to do this after the 1st qmake? qmake -o src/Makefile src/src.pro
Yes, your suggestion works and solved my problem. Nice program.
On debian qt3 is not in /usr/qt/3/ but in /usr/qt3/ or well... it is on my half package half self compiled system. Further, my qt is multithreaded and the makefile assumes -lqt where in my case it is -lqt-mt. How about configure? :)
Try to do a $(QMAKE) -o Makefile passwordcreator.pro before make and make install.
a noob but...: root@rockhound passwordcreator # make install ( [ -d src ] && cd src ; grep "^qmake_all:" Makefile && make -f Makefile qmake_all; ) || true ( [ -d src ] && cd src ; make -f Makefile install; ) || true make[1]: Entering directory `/home/martin/temp/passwordcreator/src' make[1]: Nothing to be done for `install'. make[1]: Leaving directory `/home/martin/temp/passwordcreator/src' ???
Ooops, seems there's no rules for install. Sorry dude, will fix it soon.
I created a similar script in php once that had 1 distinguished feature: all generated passwords were pronouncable. In my experience users tend to stick to the initial passwords more often if they can pronounce it! Would be nice to add. The algorithm for creating a readable password I came up with: array C are Consonants array V are Vowels array A are C+V 1. Choose a random char from A 2. if (previous 2 chars were 2xC or 2xV) choose from 'the other side' else: 1. 3. if char is last char: never end with double V. It's not foolproof, but a nice start. Additionally you could replace all characters that look like numbers. e.g. i = 1, e=3, s=5, z=2 etc... The script: http://www.mrvanes.com/randpass.php
Nice idea. You're the second one to ask me that. Task is on the TODO list. Watch for the next relese ;-)
Now implemented ;-) but must be a little bit tweaked.
Oh, and I forgot: it should never start with double Vowel as well... looks ugly and is hardly pronouncable ;)
done.
Hi Neptune, Great little tool you have here. Had a little compilation problem. Had to include unistd.h in src/passwordcreator.cpp so that the call to getpid() worked..
Hmm, thanks for the information. I don't need this include on my machine, but i'll commit this change immediately. I'll try to find from wich include I got getpid() declaration.
Would it be possible to add sometinhg like "How-Easy-To-Hack"-status. If you have only numbers, it may be easier and then, somewhere, there could be a bar or a text "98.392 % safe" or something like that. Hmm you understand? =/
Hmm, I understand perfectly ;-) Nice idea, I'll put it on the TODO list. Note that no password will never 100% safe. Too many people write them on post-it ;-)
Your request is now implemented. It will be available for the next release.