News for hackers. Stuff that matters.
Re:Why I no longer have an old-school cert on my HTTPS site by deepsun on Saturday May 24, 2025 @03:15AM (#44079353)
Some parsers, like PHP, may treat 65537 and "65537" the same. Room for vulnerability.
Re:Why I no longer have an old-school cert on my HTTPS site by int_19h on Saturday May 24, 2025 @03:48AM (#44079540)
Why would they do so? It's semantically distinct JSON, even JS itself treats it differently?
Re:Why I no longer have an old-school cert on my HTTPS site by hiciu on Saturday May 24, 2025 @04:07AM (#44079630)
It's PHP. Handling numbers in PHP is complicated enough that a reasonable person would not trust it by default.

https://www.php.net/manual/en/language.types.numeric-strings...

Re:Why I no longer have an old-school cert on my HTTPS site by int_19h on Sunday May 25, 2025 @02:37AM (#44086028)
I know that PHP will treat a string as if it were a number if you try to use it in a context where number is expected; JS does the same thing. But why would that affect JSON deserialization in a way that makes numbers and strings indistinguishable in principle (causing the loss of precision as described here)?
Re:Why I no longer have an old-school cert on my HTTPS site by dwattttt on Saturday May 24, 2025 @07:06AM (#44080262)
Time for a trip to the Abbey of Hidden Absurdities.

http://www.thecodelesscode.com/case/161