News for hackers. Stuff that matters.
Re:Take potentially dangerous PDFs, and convert them to safe... by dfajgljsldkjag on Wednesday January 21, 2026 @06:00PM (#46712881)
I personally just upload them to google drive. It would be a serious pwn if they could somehow still do a compromise through google drive.
Re:Take potentially dangerous PDFs, and convert them to safe... by bob1029 on Wednesday January 21, 2026 @07:25PM (#46713626)
Does google drive apply any transformation over the PDF, or are you effectively loading the same document in your browser on the round trip?
Re:Take potentially dangerous PDFs, and convert them to safe... by Gigachad on Wednesday January 21, 2026 @08:14PM (#46713940)
They have some kind of virus scanner for files you open via a share link. Not sure about the ones you have stored on your own drive unshared.

But probably the main security here is just using the chrome pdf viewer instead of the adobe one. Which you can do without google drive. The browser PDF viewers ignore all the strange and risky parts of the PDF spec that would likely be exploited.

Re:Take potentially dangerous PDFs, and convert them to safe... by autoexec on Wednesday January 21, 2026 @10:11PM (#46714811)
And yet browser PDF viewers still have vulnerabilities and hackers keep finding sandbox escapes.
Re:Take potentially dangerous PDFs, and convert them to safe... by venusenvy47 on Wednesday January 21, 2026 @08:28PM (#46714038)
I often view PDFs in Drive, and it's definitely not just displaying the document with the native web browser. It is rendered with their "Drive renderer", whatever that is. They don't even display a simple .txt file natively in the browser.
Re:Take potentially dangerous PDFs, and convert them to safe... by gleenn on Wednesday January 21, 2026 @07:09PM (#46713513)
Do you have any specifics on what Drive does? Any examples of it fixing embedded virii? Or is this blind assumption?
Re:Take potentially dangerous PDFs, and convert them to safe... by akersten on Wednesday January 21, 2026 @07:14PM (#46713549)
I assume they mean "upload to drive and use the web based reader to view the PDF," not "upload to drive and download it again"
Re:Take potentially dangerous PDFs, and convert them to safe... by gleenn on Wednesday January 21, 2026 @08:10PM (#46713920)
And what special sauce does the web preview use? At some point, someone has to actually parse and process the data. I feel like on a tech site like Hacker News, speculating that Google has somehow done a perfect job of preventing malicious PDFs beckons the question: how do you actually do that and prove that it's safe? And is that even possible in perpetuity?
Re:Take potentially dangerous PDFs, and convert them to safe... by dfajgljsldkjag on Wednesday January 21, 2026 @09:31PM (#46714507)
It's an image sent from Google.
Re:Take potentially dangerous PDFs, and convert them to safe... by fc417fc802 on Wednesday January 21, 2026 @10:02PM (#46714726)
> how do you actually do that and prove that it's safe?

Obviously you can't. You assume it's best in class based on various factors including the fact that this is the same juggernaut that runs project zero. They also somehow manage to secure their cloud offering against malicious clients so presumably they can manage to parse a pdf to an image without getting pwned.

It would certainly be interesting to know what their internal countermeasures are but I don't know if that's publicized or not.

Re:Take potentially dangerous PDFs, and convert them to safe... by nl on Wednesday January 21, 2026 @10:33PM (#46714962)
It certainly reduces the concern of PDF viewer vulnerability that allows local execution access which is the concern here.
Re:Take potentially dangerous PDFs, and convert them to safe... by creatonez on Wednesday January 21, 2026 @09:14PM (#46714388)
Firefox has a builtin PDF reader, PDF.js, that resides inside of the Javascript sandbox. In theory, it's as safe as loading a webpage.
Re:Take potentially dangerous PDFs, and convert them to safe... by autoexec on Wednesday January 21, 2026 @10:05PM (#46714752)
So not actually all that safe since sandbox escapes happen all the time. PDF.js has had many vulnerabilities as well
Re:Take potentially dangerous PDFs, and convert them to safe... by apyrgiotis on Thursday January 22, 2026 @04:46AM (#46717106)
(disclaimer: one of the Dangerzone devs)

That's something I do from time to time as well. AFAIK Google Drive renders all documents on the server-side (which implicitly means that they don't trust the browser sandbox), so that's a reasonable price to pay for less privacy.

Dealing with sensitive documents though is another story, you just can't upload them to a third-party service. That's where projects like Dangerzone come into play.