On 8/25/24 11:27 AM, E. Liddell via tde-users wrote:
Encrypted: yes (print:yes copy:yes change:no
addNotes:yes algorithm:AES-256)
The issue seems to be our dear kpdf not interpreting the pdf parameters
correctly. I strongly suspect kpdf has no idea how to handle AES-256 encrypted
data (was likely not part of .pdf in 2005 timeframe) It may also be not
handling the print:, copy:, change:, addNote: restrictions correctly either.
Wherever the failure occurs it is tipping the password prompt in hopes of
correcting it.
xpdf, firefox, etc. have likely been updated to handle the new restrictions
and encryption correctly.
Time for a bounty on kpdf (or grab from current occular if possible and backport)
--
David C. Rankin, J.D.,P.E.