Adobe Putting PDF Reader In a Sandbox
Captain Eloquence writes "The next major version of Adobe's PDF Reader will feature new sandboxing technology aimed at curbing a surge in malicious hacker attacks. The initial sandbox implementation will isolate all 'write' calls on Windows 7, Windows Vista, Windows XP, Windows Server 2008, and Windows Server 2003. Adobe security chief Brad Arkin believes this will mitigate the risk of exploits seeking to install malware on the user's computer or otherwise change the computer's file system or registry. In a future dot-release, the company plans to extend the sandbox to include read-only activities to protect against attackers seeking to read sensitive information from the user's computer."
I have only Sumatra PDF on my Windows 7 machine. I don't have a copy of Adobe's viewer on the machine at all.
Sumatra PDF is dumb, but reasonably secure. It can't do cut and paste, it doesn't do forms, and it doesn't have Javascript.
That piece of bloatware should be put on a harsh diet before that.
Sometimes, life itself is sarcasm...
It appears Adobe finally realized that a document reader shouldn't have access to my entire sysetm.
Why does a PDF viewer need to give the document the ability to write at all?
Would ripping some of the crazy features out of the PDF spec solve this more completely and reasonably?
What do we use PDFs for which involves writes?
Should it be an operating system feature to force all user applications to run in a sandbox by default?
Honestly, give up on Adobe Reader. There are other options. FoxIt has about the same feature set, and CAN do all the dangerous boneheaded stuff like embedded javascript and external execution, but by default it's off, and the vast majority of people never need that stuff.
On the skinny end there's Sumatra (too skinny for me, no browser plugin). At the other end is Nitro PDF, which has a TON of features even in the free version.
Honestly, just take Adobe reader right off your machine. Do it now.
Comment removed based on user account deletion
A sandbox doesn't matter if said sandbox has as many flaws as the orignal reader...
TIDserve gets right past virtualization. It uses a privilege escalation in IE to find the virtual OS' drivers and then it follows the driver chain down to atapi.sys (which it can exploit).
Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
My cat's sandbox is the right place for Adobe's products.
Too heavy, too slow, too buggy, too dangerous, etc.
-- Rastignac was here.
IANAMCSE but.....(I am not an MCSE :) )
Is there just no possible way to develop software that is NOT exploitable?
Tweet, tweet, all id10t's out of the gene pool, open swim is over.
Sounds suspiciously Apple-like. iPhone apps do this very thing.
No shit Sherlock: sandboxing, emulation, memory and hardware virtualization, CPU ring modes are all Apple inventions from 1970s and Windows 7 you're browsing from right now has its code base from Apple Lisa of that era.
It seems that Microsoft already went through this 15 years ago with Word macros. It's kind of scary that these companies that are producing software for looking at / creating documents would enable this sort of functionality in their file formats. I realize that there are a handful of applications where it's beneficial to have a document be able to write to the filesystem, but for 99.99% of documents, what business do they have reading or writing anything?
It would be like if you bought a book, sat it down on your desk, and when you pick it up later, you find that the book was doodling on your desk the whole time.
Sure there are free pdf readers that work on Linux and 64 bit, but I find that none of them are as flexible with regards to printing options as Acrobat is.
And the last time I installed multi-libraries on my system supporting both 32 and 64 bit, primarily just so I could use Acrobat, I started having some stability issues that I would just as soon not repeat.
File under 'M' for 'Manic ranting'
Just sayin'...
Edith Keeler Must Die
Who sandboxes the sandboxers?
These are my friends, See how they glisten. See this one shine, how he smiles in the light.
And Apple Stole every aspect from the XEROX PARC development. They guy credited with creating the GUI and Mouse worked for Xerox, not Apple. Xerox let them steal it, no question, but don't give credit where it's not due, PARC is responsible for far more than what you are crediting to Apple. The only thing Apple did was make these software interfaces cost effective by using commodity hardware instead of PARC'a tendency to use specialty hardware.
No, don't worry. Because of how bloated Acrobat Reader already is, Adobe was able to fit a re-skinned copy of virtualbox, containing a minimal linux image running Evince, in a package smaller than the prior download.
This is how they managed to get a "sandboxed" PDF reader out in less than the usual absolutely glacial Adobe development timeframe...
Sandbox A will be put inside Sandbox B, and Sandbox B will be put inside Sandbox A. Problem solved!
Corruption is convincing someone that the selfless ideal is the same as their selfish ideal.
"Yeah, hi. Can you please change your workflow and the way you've been doing things for years that has worked with no problems just because I can't be bothered installed a free program to open your PDF files? Thanks!"
Well if Sumatra doesn't do it for you I give my customers Foxit which has safe mode built in which halts executable code in PDFs by default, which is of course how they hit you with malware in the first place. Why Adobe decided executable code was just gravy for a document format, I'll never know. But that link will install any of the programs on their page with no toolbars, including Sumatra or Foxit, all automated. Great for setting up a PC for the first time. After version 6 Adobe became just too bloated for me to recommend to customers, but I've not gotten any complaints with Foxit.
ACs don't waste your time replying, your posts are never seen by me.