The article is *more* confusing than the original vuln report, which clearly stated the vulnerable config. By dressing it up in all that superfluous info, you dilute the message of the limited impact. More info is appreciated *only* when you take care to keep the message clear.
-
This Tweet is unavailable.
-
-
This Tweet is unavailable.
-
It only affects configurations that restrict access as root *but allow access as -1*, i.e. use ALL. The way you phrase it it sounds like it affects any config that allows access as a user or group that isn't root.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @unix_root and
You also mention "arbitrary commands" while any config that allows "arbitrary commands" as ALL, !root is already almost certainly vulnerable per se and a terrible idea and nobody should be doing that.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
If nobody should be doing that then hopefully nobody is doing that, which makes the impact minimal, which means it's your job to minimize confused panic from those who might misunderstand otherwise.
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
I had at least 5 people link me the sudo bug, some directly via your article, because they though it was some huge security hole affecting many Linux systems.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @unix_root and
Some of them even ran their own confused tests and thought it was really that bad, because sudoers is confusing and they didn't understand exactly what config they needed to have. They often accidentally gave themselves ALL outright.
1 reply 0 retweets 0 likes
(a negative control would've caught that mistake, but people rarely do negative controls when trying to quickly confirm a confusing security vuln report from the internet)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.