Yes.Just to be clear: the current implementation of FileVault encrypts the entire hard drive, effectively neutralizing this vulnerability, correct?
Yes.Just to be clear: the current implementation of FileVault encrypts the entire hard drive, effectively neutralizing this vulnerability, correct?
Is this (CleanMyMac) a trusted app?Without wanting to endorse a product that provides a "solution," CleanMyMac users might be interested to know that they can manually clean the QuickLook cache using the "System Junk" clean function of the app.
View attachment 766773
The bug lies with Apple’s code
Seems like a pretty minor issue in my opinion.
For anyone who uses Alfred, by the way, you can enter terminal commands right into the search window by starting with a ">" character and then entering the terminal command you want to run. It'll call up a Terminal window and enter the string for you right away. Makes this command even faster to run, until such time as the bug properly fixed.
It's encrypted at rest. So if the computer is booted someone could walk up and access the files. Even the lock screen is not enough for a determined person. If the computer is powered off it should be fine with a sufficiently strong password.
It's a one line command (in terminal) to clear the cache. You need to be an "admin" user, but you don't need to be root:
qlmanage -r cache
Of course, someone here will figure out a reason to whine about having to do this.
Onyx also provides this functionality.
I prefer "Think Indifferent".Think hopeless. New motto.
Ordinary people wouldn’t know to input a terminal command, or even know that Quick Look is leaking their data.
The bug lies with Apple’s code. How is this the fault of the consumer? The consumer is certainly not the party to blame in this situation.
I prefer "Think Indifferent".
Any idea how to do this?
It doesn't change the fact the software should not be working like that, and having to do a terminal command or Automator script, no matter how minor, still doesn't change that. Why is it so controversial to accept that it is a bug that hasn't been fixed in years?Those “ordinary” people would not have encrypted volumes for one, and they don’t have spyes hunting them in the first place, too. It’s a non issue and if it’s a issue for SOME, they know how to solve it.
Because it’s sensationalist news.It doesn't change the fact the software should not be working like that, and having to do a terminal command or Automator script, no matter how minor, still doesn't change that. Why is it so controversial to accept that it is a bug that hasn't been fixed in years?
I prefer "Think Indifferent".
Wardle recommends that users concerned about unencrypted data storage clear the Quick Look cache manually whenever a container is unmounted, with instructions for this available on Wardle's website. It's also worth checking out Wardle's site for full details on the Quick Look bug.
It's a one line command (in terminal) to clear the cache. You need to be an "admin" user, but you don't need to be root:
qlmanage -r cache
Of course, someone here will figure out a reason to whine about having to do this.
The referenced file* does not appear in a search of my Mac, so I wonder about the accuracy of this article.
The Library does have cache files that begin with com.apple.QuickLook, but they are tiny 53KB and 33KB.
–––––––––––
*com.apple.QuickLook.thumbnailcache
Is this (CleanMyMac) a trusted app?
By the way, I have found that some of the PDFs I have saved for documentation of work I have done are BLANK when I attempt to view them using Quick Look.
Just to be clear: the current implementation of FileVault encrypts the entire hard drive, effectively neutralizing this vulnerability, correct?
I’ve known about this for years. I accidently locked a word file and was able to “rescue” it by hitting the space bar.
Great security.
It's just that FileVault needs to be bypassed before accessing the thumbnails db.
This is Tim Cook-class half-truth nonsense.This is simply not true. Software has bugs and Apple will fix them, better than others. A tiny software bug that will be fixed isn’t a referendum on the state of the Mac every single time.
Apple doesn’t update hardware based on what you think is appropriate. They have all the data and facts to back up their strategy, which is working.
Mac revenue is still holding strong, up slightly y/y. Mac is <10% of their revenue but still a large ~$25B/yr business. They do care, but Apple understands what they’re doing. The vocal minority isn’t reality. If it were a major emergency, you’d see them update the various Mac lines. The reality is, it’s just not an issue.
This is Tim Cook-class half-truth nonsense.
Every other pc vendor owning a 25B/yr business would run around the world to get new at least 10 new models out yearly, do innovation, fix hardware shortcomings, design better keyboards, ports, listen to users etc. instead of lamenting, yearning, pretending to be the greatest media company, amongst all other overblown but mediocre side-activities.
A tiny bug may not be a referendum of the Mac‘s state, but a symptom like so many others.
Nobody would be complaining if a focused product guy would run the company instead of a country-club manager