News for hackers. Stuff that matters.
Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har... by de_watcher on Friday April 17, 2020 @03:28AM (#22896958)
"You have a poisoned view"? That's just your opinion. I tried to base mine on a somewhat objective observation about speeds and volumes of stuff happening.

"Everything bad has something to do with javascript"? Don't put words in my mouth.

"A C# developer at Microsoft" plus a javascript explosion. Aren't you just confirming my point? Those new people didn't materialise out of thin air, they may have been software developers who had to change focus rapidly. And they didn't necessarily knew how their creations could be misused under the rules of that new javascript world.

And he doesn't look old enough to be a designer of POSIX threads.

(if you don't like my expression about the "vibe" then I'll give you an example of a protocol with a C vibe: the type value would be a fixed-length field with a table of integer IDs written in the standard; everyone would complain about integer sign, wrap-arounds and the new extension field that was added because we ran out of IDs)

Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har... by ZenPsycho on Friday April 17, 2020 @03:40AM (#22897011)
This is conspiracy theory logic. You could literally use this same line of argument to blame anything bad on a vague "explosion of javascript", fact free. Not very impressive either since it relies on smearing people's competence and professionalism based on handwaving instead of any kind of serious engagement with the facts of the situation. Moving on.
Re:Auth0 JWT Auth Bypass: Case-Sensitive Blacklisting Is Har... by de_watcher on Friday April 17, 2020 @03:55AM (#22897079)
Numbers of developers and code aren't vague. They are disproportionately significant. And you don't even use arguments, just a low-effort labeling.