News for hackers. Stuff that matters.
Re:If your code accepts URIs as input, filter out “file://” by wkd on Monday September 12, 2016 @07:15AM (#12478726)
"Despite reporting the problem to the author on Friday, and following up the report via Twitter this has not yet been fixed, but after four days I assume I'm not alone in spotting this."

Giving someone a weekend to fix something doesn't exactly sound like responsible disclosure. I understand if you get excited because you found a flaw but if you find something like this please be more responsible with publishing your findings.

Re:If your code accepts URIs as input, filter out “file://” by kuschku on Monday September 12, 2016 @07:44AM (#12478860)
Well, I found the same by pure chance before reading this article, and I suspect many more in the HN crowd did.

If already half a dozen people on HN report they’ve found it and emailed the person about it, it’s likely it’s too late for responsible disclosure.

Re:If your code accepts URIs as input, filter out “file://” by 4ndr3vv on Monday September 12, 2016 @08:43AM (#12479183)
Agreed! Better get that karma before someone else does /snark
Re:If your code accepts URIs as input, filter out “file://” by kuschku on Monday September 12, 2016 @08:45AM (#12479190)
The issue is more that if so many people have already found it, who else has?
Re:If your code accepts URIs as input, filter out “file://” by 23andwalnut on Monday September 12, 2016 @10:37AM (#12480012)
Disclosing it publicly before it's been fixed only increases the number.