Re:I couldn't debug the code because of my name
by pferde on Wednesday October 20, 2021 @05:37PM
(#28937050)
I have seen a windows app with a text field whose max character count was somehow determined by system font size - probably a crude way to make sure the entered text fits the hard-coded field size.
The problem was that this field was used to enter a 10-digit code, and as it turns out, on default Windows10 system, the fonts are set up so that this field only fit 8 of them. Oops! :)
Re:I couldn't debug the code because of my name
by munk-a on Wednesday October 20, 2021 @05:41PM
(#28937107)
I'd like to see how that App would work with me sitting here fonts cranked up to 175%. I've never heard of a setup like that though - it sounds like it'd be surprisingly intricate to actually configure.
Re:I couldn't debug the code because of my name
by joe_guy on Wednesday October 20, 2021 @09:17PM
(#28939090)
Not fully related but you reminded me of this.
Around the time of AOL3 or early AOL4 someone found a user name exploit.
When making a new account, on the client side use winapi's EM_LIMITTEXT to bypass the max character limit on the input textbox. Enter one or two letters, a bunch of spaces, then some more letters.
The server side would truncate to the original length, leaving you with a one or two letter username, working around the 3+ requirement.
Re:I couldn't debug the code because of my name
by munk-a on Wednesday October 20, 2021 @04:46PM
(#28936283)
I maintained a system where we had unbounded password length... but only respected the first six characters of the password. (we did fix that).
Re:I couldn't debug the code because of my name
by aidenn0 on Wednesday October 20, 2021 @07:08PM
(#28938043)
Unix passwords worked that way for 8 characters for many years due to the crypt algorithm used.
Re:I couldn't debug the code because of my name
by stzsch on Wednesday October 20, 2021 @08:07PM
(#28938547)
IIRC VNC passwords are still like this.
Re:I couldn't debug the code because of my name
by bradknowles on Friday October 22, 2021 @03:21AM
(#28954479)
Sounds like some banks I’ve heard of.
Re:I couldn't debug the code because of my name
by TechieKid on Wednesday October 20, 2021 @11:53PM
(#28940031)
Discover (discover.com) currently has a similar bug where it'll allow me to login with my password, but will not accept the same password in the 'Change password' workflow as the old password, complaining about it being invalid. (shrug)
Re:I couldn't debug the code because of my name
by kevinmgranger on Wednesday October 20, 2021 @04:26PM
(#28936013)
You're lucky they weren't different lengths in the backend. I've been bitten by that surprise one too many times (which is any number higher than zero)
Re:I couldn't debug the code because of my name
by aidenn0 on Wednesday October 20, 2021 @04:30PM
(#28936050)
The most ridiculous thing is the UI for setting the password even said "X-Y characters long, must include at least one..." but the login page could not support Y characters.
Re:I couldn't debug the code because of my name
by a1369209993 on Thursday October 21, 2021 @01:29AM
(#28940679)
> one too many times (which is any number higher than zero)
Nitpick: if the number is higher than one, then it's at least two times too many.
The symptom was that I could login if I used my password manager browser plugin, but not if I pasted it from my password manager.