Naughty Strings: A list of strings likely to cause issues as user-input data

Creator/Maintainer of the repo here. I apologize for the lack of updates to the BLNS. (since I'm free today and this is on the HN front page, I'll do a cleanup pass). Even though it's a GitHub repository with 12.3k stars, there's not much to say or improve on what is effectively a .txt file based around a good idea (I recently removed mentions of my maintainership of the BLNS from my resume for that reason, despite its crazy popularity).

Big lists of previous comments: https://news.ycombinator.com/item?id=13406119 https://news.ycombinator.com/item?id=10035008

Most of what I do involves the messy world of text, and I think this is a great resource. I wish the software I depended on tested against it. I can think of a few more cases that I've seen cause havoc: - U+FEFF in the middle of a string (people are used to seeing it at the beginning of a string, because Microsoft, but elsewhere it may be more surprising) - U+0 (it's encoded as the null byte!) -…

Solid list for a quick SQL injection and XSS reference with lots of examples. Even unicode/accents/two-byte characters etc are super useful to check handling on all the way from the front-end to the persistent storage solution (DB, etc). Lost it laughing at "Human Injection" section: > # Strings which may cause human to reinterpret worldview > If you're reading this, you've been in a coma for almost 20 years now. We're trying a new technique. We don't know where this…