Re:What Happened: Adobe Creative Cloud Update Bug
by mirimir on Monday February 15, 2016 @08:26AM
(#11103235)
They obviously made no check. The goal was probably to delete all Adobe configuration files. And somehow the first hidden folder in home became a target. Because .adobe is obviously going to be first, right?
[ Parent
| on HN ]
Re:What Happened: Adobe Creative Cloud Update Bug
by ajanuary on Monday February 15, 2016 @10:09AM
(#11103717)
Deleting the first directory seems like a harder problem than deleting a folder called .adobe.
Re:What Happened: Adobe Creative Cloud Update Bug
by mikeash on Monday February 15, 2016 @11:10AM
(#11104083)
I don't know about that. It's harder to do it right, but they probably didn't bother with doing it right.
For example:
ls / | head -n 1 | xargs rm -rf
Re:What Happened: Adobe Creative Cloud Update Bug
by ajanuary on Monday February 15, 2016 @05:46PM
(#11106639)
That's easier than
rm -rf /.adobe
?My point being that things indicate a more interesting problem they were trying to solve than just deleting a directory. What that actually was, and how that lead to such an awful solution, would be interesting to know.
Re:What Happened: Adobe Creative Cloud Update Bug
by mikeash on Monday February 15, 2016 @06:05PM
(#11106751)
I agree it's pretty far fetched. I'd love to know what the real story is too.
Re:What Happened: Adobe Creative Cloud Update Bug
by kevb on Monday February 15, 2016 @03:11PM
(#11105595)
I wonder if it was something like .adobe-A3DF0910 that they were targeting, so they couldn't completely hard code the path and neglected to hardcode the prefix. Or maybe it was a purely randomly named directory without any prefix.
Re:What Happened: Adobe Creative Cloud Update Bug
by mirimir on Monday February 15, 2016 @10:54PM
(#11107796)
Maybe they were targeting .adobe* in home, and assumed that it'd be first, but didn't account for that possibility that it'd be missing. That would have been insane, I admit. But we do know that initial dot directories were getting hit.