Microsoft to Replace Edge’s PDF Reader with Adobe Acrobat
theregister.com
theregister.com
Adobe's products have been a source of endless security vulnerabilities, and no matter how much sandboxing you do it is intrinsically unsafe.
The first best thing would be for PDF to die, but the second best thing would be pdf.js
If you care about security, turn off this feature and use the pdf.js extension. If you absolutely need form-filling, then run the standalone adobe reader and uninstall it at the earliest possible time.
The next best options would be open source document formats.
EPUB, ODT, SVG, exported HTML like MHTML (MHT)... all good options.
There's whole industries out there where the immutability of PDF is a feature, not a bug.
Even for such things as contracts, something like PandaDoc or DocuSign is way better than PDF.
I mainly see PDFs used for sending documentation, HR onboarding info, and contracts. None of those uses require immutable files, and they are easy to become obsolete.
Paid e-books could also be done through web readers. But EPUB exists.
For archival purposes, I recognize that there is a use for files, and I listed some options that are all better than PDF.
A PDF reader requires complexity on the order of a web browser. It has enormous amounts of legacy baggage. And it is proprietary and still adding more features regularly. Its existence is akin to that of Flash. It comes from an era where web standards were immature.
in reality what we need is a better standard
If you are distributing code, will you share it via tarballs and zip files, or will you share it via a hosted service like GitLab or GitHub? Most people undestand that the latter is superior in every way, and you can still have the offline archives via having a full clone of the repo locally.
I would argue that the same logic applies generally. If you share your resume, it would be smarter to use a static github page tied to a git repo, than it would be to simply email a file. That file may have a typo or become obsolete. And in reality you are likely trusting email service providers anyways... ie the cloud.
Having a full archive of it locally with a local git repo means you actually aren't locked into them. My use of the term cloud was meant to be a fully general concept, and I wasn't advocating any particular locked-in concept. I'm simply advocating leveraging specialization of labor.
If you sew all your own clothing, build you own house, build your own car, etc... then by all means, run your own email servers, send zip files, and write your own operating system. Definitely keeps your trust surface low.
I mean, there's nothing special about that, it's just a very limited word processor that uses the ginormous web stack for rendering.
Pretty much impossible to map most usages of PDF to that.
FWIW, I believe pdf.js has some support for forms nowadays, though I haven't used it personally/don't know how complete it is.
https://blog.mozilla.org/attack-and-defense/2021/10/14/imple...
Fta: Microsoft made a particular point of outlining its efforts to ensure the new Adobe PDF tool is secure. Miscreants will use malware-infused PDFs to muscle their way into enterprise networks, so Microsoft's Edge Vulnerability Research team was involved in the process of bringing the Adobe engine to Edge.
That includes adding security features to the PDF stack such as PartitionAlloc a secure heap implementation developed on Chromium and already used in Edge, according to Gareth Evans, principal security research lead at Microsoft.
"PartitionAlloc is designed in such a way as to keep objects of different types separate from each other with minimal intervention from the developer," Evans wrote.
The package also includes mitigations such as Intel's Control Flow Enforcement Technology to protect against the hijacking of control-flow transfer instructions, a technology that complements Microsoft's Control Flow Guard. Fuzzing – automatic testing for vulnerabilities – is another security feature included with the new Edge PDF stack.
In addition, Edge's Acrobat engine will be included in the software vendor's bug bounty program to incentivize developers to find and report flaws. And there have been quite a few flaws in Adobe's PDF code.
"Don't worry guys, all the buffer overflows will lead them nowhere!"
Open up the hamburger menu, you'll see games, shopping comparisons, etc. It feels like 90s adware. I'm not surprised they're turning PDF reading into a paid advertisement for Acrobat.
Afaik Windows doesn’t ship with a default PDF viewer other than Edge’s, so they probably made a pretty sweet deal with Adobe to let them in to upsell their subscription.
Also saw something new recently: got some “tips” in some sort of in-browser notification drawer, again asking to be set as default. Apparently denying synchronous dialogs as you open the browser aren’t enough, you should get nagged asynchronously as well.
Of course, when you check out their recent Bing Chat, you’ll be asked to set the entire Microsoft suite as default, plus installing their mobile apps, so that you can be bumped up in a completely opaque waiting list.
I switched to Edge and Bing a few years ago and don't at all regret it. Switching was painless, the browser uses much less CPU on windows, it syncs across all devices including mac, all the chrome extensions still work, and search results on bing are better than google in my testing.
I switched to Edge on Mac from Chrome this week for one reason and one reason only: In full screen, Edge properly displays the addressbar when the cursor is moved to the top of the screen, while Chrome still cannot do this. (No, I do not want to enable "Always Show Toolar in Full Screen".) My understanding is that this is a very, very, very longstanding entry in Chrome's bugzilla.
The transition was easy; Edge even handled extensions correctly, pulling extensions from the Edge store when possible (except when versions differ, which I noticed in two cases) and from the Chrome store for the rest. Even extension settings came over. The only flaw I saw was that Edge only imported tabs from one Chrome window; I had to bookmark all tabs in each window, reimport bookmarks into Edge, then reopen each set of bookmarks into its own window.
go figure...
Rather, they already were shipping a PDF reader, as most browsers already do. But were likely inundated with bug reports about how it was broken for advanced workflows like form filling.
This solves that problem and likely Adobe consented without much cajoling to cement the relevance of a premier product of theirs.
Also, Microsoft is currently acquiring Activision, so Candy Crush is very nearly a Microsoft product.
Same for the edge shortcut on the desktop.
The funny thing is, only Acrobat Reader on PC and Mac is like that. If you open some of the weird PDFs on their phone Acrobat Reader or web Acrobat Reader, they are about as broken as they are in Pdfium (Chrome’s open source PDF reader, based on licensed FoxIt) or Preview, let alone pdf.js.
Not even Adobe can really port their format readers on phone and javascript.
(But that’s my experience with Word/Excel too)
Yes, it seems that they are: https://en.wikipedia.org/wiki/Foxit_Software
Where this gets really weird is Office 365 integration, if you export as PDF in word and have the "Open after exporting" checkbox ticked, it'll try and force it into Edge even if you have Sumatra as the default reader in Explorer, resulting in Edge _downloading_ a copy of the file to the downloads folder even though the original is in the same folder as the word doc on your local drive.
I imagine the Adobe integration will only make opting out even harder. Maybe it's time to switch back to chrome or one of the million lookalikes.
As I stated in a comment, Chrome uses Foxits code under the hood, so I don't understand why they don't use that.
Maybe it's not licensed for use with forks. Aka Chrome vs Chromium
Windows is looking like the OS that they would use in Idiocracy now.