this post was submitted on 28 Jun 2023
1 points (100.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54565 readers
531 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You're doing it wrong. PDF with embedded javascript is a nightmare and it still doesn't make PDF equal to excel.
Better generate your documents with your favourite HTML templating engine from your DB and convert them to simple PDF in the last step.
Only had that experience with badly designed, macro ridden documents which there's no excuse for anyway nowadays. I use a lot of print templates (various label printers) and it works flawlessly.
Also, exporting a non MS file format usually imports fine in LibreOffice, even with complex documents.
The ability to quickly edit PDF makes it the office suite of my choice.
Yeah, but if your boss or client sends you a document that doesn't work you're not going to tell them "Uh well this is a badly formed document and you shouldn't embed scripts and it's your fault that my FOSS alternative application can't work with this". At least I hope you're not.
Of course I do and I expect my employees to report such incidents to IT. Such documents are common attack vectors.
In my experience, customers are not aware of failing interoperability or possible security threats and often grateful for such hints.
There's a reason why libreoffice (and I guess other office suits aswell), evince or antivirus show a big, fat warning when opening such documents. Surely there are cases were macros are useful or necessary, but if they have to leave the company, you're doing it wrong.
This talk might be interesting for you: https://www.youtube.com/watch?v=4F2xMw3987I
The accounting department loves you. I'm sure the government will bow down to your demands, respect your security concerns, and adopt a more secure approach swiftly.
If you must deal with an organization that doesn't give a shit about security, then you're SOL. We live in the real world. If you don't submit the government forms how they want you to, they shrug and fine the shit out of you. They couldn't care less about the security risks their workflow poses on you.
You can mitigate the risks, but you never have absolute control. While Acrobat poses a security risk, not having Acrobat poses a business risk.
Then you just don't know the law. There is no legislation that enforces Acrobat in any civilized country without alternative.
Quite the opposite: Send macroridden documents to any decently secure infrastructure and you get a big fat warning in the subject if it's not filtered entirely. Officials LOVE to do that extra call ensuring that this document is really from you before opening it and no phishing attempt...not.
Source: working >25 years in IT, >15 years for government IT
EDIT: we got some real Adobe Acrobat Fanboy here, eh? ;-)