3 ms·
Which gives (except for pdf.js) more PDF readers written in C, some with a long history of CVEs, and typically not sandboxed by default. Since many people are
by danieldk 8y ago
Which gives (except for pdf.js) more PDF readers written in C, some with a long history of CVEs, and typically not sandboxed by default.
Since many people are using a PDF reader to read PDFs from relatively untrusted sources, do yourself a favor and at least use a reader that does not have full system access.
macOS: Preview.app (uses macOS sandboxing)
Linux: Evince Flatpak on Wayland (Flatpak uses sandboxing. Wayland because X11 apps can read all keystrokes, mouse events, do screengrabs.)
Windows: no clue
All platforms: in-browser PDF reader with a browser that sandboxes.
- rvp-x 8y agoIf you're counting on wayland to sandbox arbitrary code execution, you're getting in trouble.
- danielhlockard 8y agoI think they're counting on flatpak.
- Spivak 8y agoApplications that can send commands to X.org servers can completely control it. The same isn't true for Wayland. Flatpak is providing the actual application sandboxing, but being allowed to talk to the X server is a huge amount of privilege that can't really be restricted.
- Santosh83 8y ago> Windows: no clue I think UWP apps are sandboxed by default, so something like Xodo PDF could be a possibility.
- Already__Taken 8y agoor Edge