Ahh, interesting... How would you structure your workflow to protect from potentially malicious PDFs? I had originally thought of setting up an inotifywait wa

Ahh, interesting... How would you structure your workflow to protect from potentially malicious PDFs? I had originally thought of setting up an inotifywait watcher that would look for downloaded PDFs to swap downloaded files (while leaving a *_with-risky-active-contents.pdf copy). After thinking for a bit about your comment, I thought about creating a .desktop file that first cleans the PDF via `docker run --runtime=runsc -it ubuntu gs ...` that then proceeds to launch the viewer, and is associated as the main reader of PDF documents... But now I am wondering if this should be integrated into clamav and other antivirus clients (and unblocking on a case-by-case basis).