I want it to use 6 words and put spaces between them. I have got something close to that by setting "Extra count" to "Always" and "Extra chars" to " ". But then it puts a space after each word, so there's a space on the end of the password that I don't want. The advice for Diceware passwords is to put a separator like " " or "-" or "." between each word, and it's annoying to have one at the end as well. I tried using "5", thinking this might be the first five, but it seems to put them in some of the time and not other times, which isn't what I want. Perhaps you could add another option to the "Extra Count" like "Between words"?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm actually working on a newer version of the plugin, where you will be able to configure it more like a Sequencer (word|char, followed by word|char, followed by word|char, .... where every word and char can be random).
You will be able to setup your requirements more easily with this version. Unfortunatly, I'm having a hard time with the graphical part; so far, the configuration can only be done by filling up the XML. Some testing still need to be done, but the generation engine is coming along well.
Are you, or do you know anyone, interested in giving me a hand for the windows form?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am not sure I like that idea, I can't picture any sort of decent UI for it, and the beauty of the word sequence passphrase is that it is simple and memorable, yet random enough to force an attacker into brute-force mode. I think I'd like better a simple 3-checkbox system:
[ ] Prefix [x] Between words [ ] Postfix
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, the UI part in the UI branch is not the most stable, plus I think I mixed up IOC changes and UI changes within the same branch... sorry for the confusion there...
But your initial post got me thinking that maybe it could have a "simple" interface that can have fewer options, and later work on an advanced interface that will allow to configure most of the xml/data structure possibilities...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I want it to use 6 words and put spaces between them. I have got something close to that by setting "Extra count" to "Always" and "Extra chars" to " ". But then it puts a space after each word, so there's a space on the end of the password that I don't want. The advice for Diceware passwords is to put a separator like " " or "-" or "." between each word, and it's annoying to have one at the end as well. I tried using "5", thinking this might be the first five, but it seems to put them in some of the time and not other times, which isn't what I want. Perhaps you could add another option to the "Extra Count" like "Between words"?
I'm actually working on a newer version of the plugin, where you will be able to configure it more like a Sequencer (word|char, followed by word|char, followed by word|char, .... where every word and char can be random).
You will be able to setup your requirements more easily with this version. Unfortunatly, I'm having a hard time with the graphical part; so far, the configuration can only be done by filling up the XML. Some testing still need to be done, but the generation engine is coming along well.
Are you, or do you know anyone, interested in giving me a hand for the windows form?
I am not sure I like that idea, I can't picture any sort of decent UI for it, and the beauty of the word sequence passphrase is that it is simple and memorable, yet random enough to force an attacker into brute-force mode. I think I'd like better a simple 3-checkbox system:
[ ] Prefix [x] Between words [ ] Postfix
You know what? I lied. I kind of like what you did in the GitHub repo. It crashes a lot on me, though...and it won't allow a space character.
Yeah, the UI part in the UI branch is not the most stable, plus I think I mixed up IOC changes and UI changes within the same branch... sorry for the confusion there...
But your initial post got me thinking that maybe it could have a "simple" interface that can have fewer options, and later work on an advanced interface that will allow to configure most of the xml/data structure possibilities...