Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@endor Yeah, IIRC just a few days or maybe a week or so later. Then they had to re-patch it.
-
"Imagine having unit tests for bug regression in security critical systems."
- this post bought to you by the MacOS Kernel Gang -
I never understood how something like that could ever happen. There is no legitimate reason to handle root logins differently.
So why do they have special code branches triggered for root before she even has been authenticated?
Do they check against an additional hash for a master password wich they had to add because of a national security letter?
And if so: Why only for root? Why not just check that hash for all user names?
Seriously not getting how you could end up with different pre-authentication code for root vs. non-root...
Related Rants
-
zemaitis7My local ISP was saving their database backups in an unprotected folder which was literally domain.com/backups...
-
PonySlaystation8There was a time in Windows 95, where during login, you could just press cancel and you were logged in without...
-
netikras15Colleagues sharing passwords.That was a big fat NO when I was a sysadmin - and for a good reason. But now, sin...
Apple released an update for MacOS that allowed you to type "root" as the username and "" as the password, hit the Authenticate button twice (the first time erroring out) and then have complete root permissions to the system.
They fixed it pretty much immediately, but then a later patch regressed it again.
rant
wk234