News for hackers. Stuff that matters.
Re:Blizzard games were vulnerable to DNS rebinding attack by Nadya on Monday January 22, 2018 @05:27PM (#16208612)
Functionally - yes. By definition - no.

A blacklist won't allow items that match and a whitelist only allows items that match. Blacklists include by default and whitelists exclude by default.

Since the regex needs to match to be included - it is, by definition, a whitelist. It excludes by default anything that doesn't match. It just so happens the net being cast is so wide as to be "all except ____" where a whitelist is usually seen as "none except ____".

Re:Blizzard games were vulnerable to DNS rebinding attack by jdoliner on Monday January 22, 2018 @05:41PM (#16208750)
I think part of the definition blacklist and whitelist is being a list.
Re:Blizzard games were vulnerable to DNS rebinding attack by Nadya on Monday January 22, 2018 @05:53PM (#16208866)
Think of it as shorthand for a list that expands to be infinitely large. [0]

People would consider a blacklist that includes ` * .example.com` to be a list that contains all potential subdomains of `example.com`. With ` * ` being seen as shorthand.

E: Spaces around the asterisk added to avoid HN formatting.

[0] Technical limitations aside, especially in the context of URL matching since URLs have a maximum character length.

Re:Blizzard games were vulnerable to DNS rebinding attack by eropple on Monday January 22, 2018 @05:55PM (#16208893)
A list of regexes is a list.

A list with one entry is also a list.