If a user types hUNTER2 and your service corrects it to Hunter2, have you reduced security? How much will it help?
This fun paper explores this Q, finding you can preserve security and fix 10% of logins:
pASSWORD tYPOS and How to Correct Them Securely https://www.ieee-security.org/TC/SP2016/papers/0824a799.pdf
miniblog.
Related Posts
Building VaccinateCA, a website developed by volunteers to make vaccination information widely available.
It's a long read, but it explores a bunch of larger policy / organisational challenges they encountered in the public sector.
https://www.worksinprogress.co/issue/the-story-of-vaccinateca/
Another interesting post where PVS-Studio explores running their tool on a major open source project, this time Android.
https://www.viva64.com/en/b/0579/
It seems like a number of these checks would be straightforward additions to OSS compilers.
Syntactic Closures by Bawden amd Rees: https://www.dtic.mil/cgi-bin/GetTRDoc?Location=U2&doc=GetTRDoc.pdf&AD=ADA195921
This 1988 paper explores an alternative Scheme macro system before hygienic macros were standardised.
