← Back to context Comment by mmoll 2 days ago The musl vulnerability looks a lot like an intentional backdoor, doesn’t it? 3 comments mmoll Reply Cakez0r 2 days ago Choosing * instead of NULL is indeed very fishy coincidence. Of all the return values they could've picked... What are the odds? Arch485 1 day ago About 1 in 256 I'd reckon procaryote 2 days ago Also the coincidence of 3 weeks later adding "oh, no passwords above 256 chars" making it easy to trigger
Cakez0r 2 days ago Choosing * instead of NULL is indeed very fishy coincidence. Of all the return values they could've picked... What are the odds? Arch485 1 day ago About 1 in 256 I'd reckon procaryote 2 days ago Also the coincidence of 3 weeks later adding "oh, no passwords above 256 chars" making it easy to trigger
procaryote 2 days ago Also the coincidence of 3 weeks later adding "oh, no passwords above 256 chars" making it easy to trigger
Choosing * instead of NULL is indeed very fishy coincidence. Of all the return values they could've picked... What are the odds?
About 1 in 256 I'd reckon
Also the coincidence of 3 weeks later adding "oh, no passwords above 256 chars" making it easy to trigger