3 ms·
I was refactoring some legacy academic code recently. It came with a GUI which, if the user did something wrong, fail with the message "Error N" (N being some n
by joshvm 11y ago
I was refactoring some legacy academic code recently. It came with a GUI which, if the user did something wrong, fail with the message "Error N" (N being some number) without any further information or logging. The only way to figure out what happened was to grep the source code to see precisely what triggered the alert box.
There's also the bizarre policy university has about passwords. Your password is reset every six months (fine), it can't be similar to your old one (fine) and it's truncated to 8 characters (what?).
- majewsky 11y agoI saw something similar when I used a German government agency's website last week to fill out some forms. Their password policy was: - minimum 8 chars - contains at least 3 of 4 of the following types of chars: - small letters - capital letters - numbers - symbols I usually use random-generated passwords that are dumped as hex, i.e. [0-9a-f]{64}, so I just added "A+" at the end. Turns out that didn't work. What did work was to prepend "A+" instead of appending it. So apparently they silently truncate long passwords somewhere before the 64th character.