with/without options are not enforced

[SeekerFS]

There are many sites that require your password to have at least one special character like a dot.
But even when i select "with . / / _" there is like 90% chance that the generated password doesn't have a single one of those characters and it's still not accepted.
So maybe add an extra with/without option - enforce with special - and that will make sure that at least one of these selected "with" will be included in the password.

[lpascal-ledger]

I see the point of this. Not sure what form it would take though.

[SeekerFS]

a simple solution would be to just add/insert/replace one char into the output after it's calculated.
for example if you select "with . / / _", it would generate the password normally, and then put a dot somewhere postprocess.

[SeekerFS]

But that would make the password needlessly longer, so here is how I'd do it, including another feature of indexing so that you could easily replace stolen passwords:

1. Add 2 options to the password properties:
   Enforce all sets - no(default) or yes
   Password index - 0(default) - 30000

2. Add 3 properties to the password entry: EnforceAllSets + Index + Offset(this one is procedurally computed at creation)

3. After typing in the key, do this before saving it (a C++ pseudocode with the pure logic):

auto password = Password(...our selected properties and key);
int index = password.Index; // This many successful password offsets will be skipped
for(password.Offset = 0; password.Offset < maxInt; ++password.Offset) {
if(password.EnforceAllSets ) {
// this addition line should be inserted inside GeneratePassword, so that we actually type and show the right password!
int key = password.key + password.Offset; // integer addition, key is the integer value of the password's keyword
auto hash = GeneratePassword(key); // this will be the password string
bool validPassword = true; // has the password passed enforcement tests?
foreach(auto s : allowedSets) {
validPassword &= hash.ContainsAnyCharOf(s); // enforcement tests
}
if(!validPassword) continue; // skip this offset, do not even attempt to count the Index
}
if(0 < --index) break; // Do not accept yet if we are skipping Index
}
if(password.Offset == maxInt) return error("Password failed. Try another."); // almost impossible unless bad code
// Now we have the last property "Offset", and can add the password entry
return password;

4. GeneratePassword (or whatever is a function that makes that hash) should add (integer +) Offset to the binary input before hashing, to make Offset 0 identical to the default offsetless. like how the line "password.key + password.Offset" is doing.

5. I would also add a new main menu entry "Edit Password", where you can select password to edit, and it will take you to the property selection, set up as that password, so you change any flags, and then you can edit the key (prefilled), and after accepting, it would rerun to point 3, and update the password entry.