as seen on cctv monitors, now cherry-flavored
remember, there's a person behind everything
| Pronouns | he/they |
| Site | https://eclair.cafe |
| Alt | @vyivel |
as seen on cctv monitors, now cherry-flavored
remember, there's a person behind everything
| Pronouns | he/they |
| Site | https://eclair.cafe |
| Alt | @vyivel |
never really thought about password normalisation before but it came up in a recent audit and now I'm kinda fascinated by it.
TL;DR if you treat passwords as byte strings in some particular encoding (say, UTF-8), and derive keys or hashes from those bytes, it breaks in a bunch of common use-cases with CJK scripts, because different input methods (e.g. desktop vs. mobile keyboard) may generate different encodings or forms/widths of the same visual characters.
adding html signatures to outlook is not the best ux ngl
(you create an empty signature in outlook, then open the signatures folder, open html files in a text editor, and replace contents with your signature. repeat this for every signature. also, if you then open such a signature in outlook, it will look off, even though it's fine in actual mails.)
something something useplaintext.email