Christian Thoeing

Hello Sylvie, Thank you for the report. Trying to reproduce the error on my system (Windows 11), PwTech doesn't load the French translation either, but I don't get any error message at all. Can you please let me know which versions of Password Tech (32-bit or 64-bit) and Windows you are using? I plan to fix this in the upcoming version 3.5.5 (to be released mid-June).

No, it is not possible to compile Password Tech with GCC. C++ Builder and its clang-based 32-bit or 64-bit compiler must be used to build the program. This compiler supports several keyword extensions to the C++ standard for compatibility with Delphi/Object Pascal. Note that the "Community" edition of C++ Builder is free for non-commerical use.

Hi John, you can exclude ambiguous characters by enabling the option "Exclude ambiguous characters" in the "Advanced Password Options" window (press "Advanced" button in main window). In the same window, you can also customize the list of ambiguous characters. Alternatively, regardless of the "Exclude ambiguous characters" option, you can select the placeholder <easytoread> in the character set box below "Include characters" (main window) to use alphanumeric characters without ambiguous ones.

Hi Paul, no, currently there's no way to remove trailing whitespace characters. I will consider this for the next version. For now you could change the format string to 2[ws2d ]ws2d to avoid the trailing space character.

Thanks for the information. I have no idea why the 32-bit executable of the current version 3.5.3 has 13 findings, whereas the 64-bit executable of 3.5.3 as well as the previous 32-bit versions (3.5.0-3.5.2) have none. All executables were built on the same, clean Windows machine. I strongly suspect that these are false positive findings, and I need to find out the cause for the 32-bit executable...

Cannot reproduce on my system - Ctrl+Shift+P works with 3.5.0. Can you please let me know what happens when you try to register the key combination?

In the main window, press the "Advanced" button, and select the appropriate "Include at least..." option(s) from the checkbox list in order to ensure that generated passwords contain at least one number, symbol, etc. Alternatively, you can use a format sequence like "{14Ads}" (permutation of 14 alphanumeric characters, 1 digit, and 1 symbol).

Why don't you just disable the "First character must not be a lower-case letter" option? Then all your password should contain exactly 1 upper-case letter. Regarding special characters, you entered <az> into the "Redefine special symbols" box, which adds the characters <, a, z and > verbatim to the set of special characters. You cannot use placeholders in this box. Instead, enter the desired characters verbatim into the box, e.g. !@,.-_+.