Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

And yet the exploit was known "for years" (so sez TFA). So which is it, security hole from a recently-added feature, or a "hole" that was an open secret for over a decade?


Both, because apparently a feature from 11 years ago is "recently added" per TFA. QuickLook has always worked this way (cached images go in /var on the boot drive).


Yeah, I was being somewhat rhetorical. :-)

cached images go in /var on the boot drive

Something so commonly-known that even I, not exactly a Darwin kernel dev, knew that. Another comment called TFA "blog spam", and I can't argue strongly that they're wrong.


blogspam is referring to the fact that TFA is regurgitating a blog (and capturing revenue) without adding value.

too bad the original blog (if it is the original) is undated.


It says "17 days ago" and if you hover changes to "02 Jun 2018" (at least on desktop)


> cached images go in /var on the boot drive

side-bar: how do you know this? is the information about the file structure of linux available somewhere? I've only ever run into this type of thing circumstantially.


The Filesystem Hierachy Standard is used by most linux distributions, and also by other unix systems:

https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard


Personally, I know it like I know a lot of things: poking around one day, probably looking for something else in the /var directory ("is it /var/log, or /var/logs?"), and "'ello, wot's this?". Best I can recall, I've never had a practical reason to know this, or a lot of other things I know.


It's something you come to learn after using command-line Linux for a while.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: