LWN.net Logo

Okular, Debian, and copy restrictions

Okular, Debian, and copy restrictions

Posted Jun 2, 2009 4:01 UTC (Tue) by Trelane (subscriber, #56877)
Parent article: Okular, Debian, and copy restrictions

The above arguments are a cop-out. It is worth noting, however, that there is a very valid reason for implementing the DRM: patent licenses. Quoth http://partners.adobe.com/public/developer/support/topic_legal_notices.html:

Accordingly, the following patents are licensed on a royalty-free, nonexclusive basis for the term of each patent and for the sole purpose of developing software that produces, consumes, and interprets PDF files that are compliant with the Specification:
A conforming reader (http://www.adobe.com/devnet/pdf/pdf_reference.html)
A conforming reader shall comply with all requirements regarding reader functional behaviour specified in ISO 32000-1. The requirements of ISO 32000-1 with respect to reader behaviour are stated in terms of general functional requirements applicable to all conforming readers. ISO 32000-1 does not prescribe any specific technical design, user interface or implementation details of conforming readers. The rendering of conforming files shall be performed as defined by ISO 32000-1.


(Log in to post comments)

Okular, Debian, and copy restrictions

Posted Jun 2, 2009 4:16 UTC (Tue) by jake (editor, #205) [Link]

So, a reader that has default behavior which is 'compliant', but can be changed to non-compliant in 4 clicks is OK? I suspect if Adobe cared, they could easily claim that Okular doesn't comply and thus doesn't have the appropriate patent license(s).

It seems a bit hard to argue that there is a *legal* basis for choosing to implement the copy bit if a way is also provided to circumvent it. Particularly one that is easily available through the UI.

jake

Okular, Debian, and copy restrictions

Posted Jun 2, 2009 4:26 UTC (Tue) by Trelane (subscriber, #56877) [Link]

It'd be against the spirit but not the words, so I'd think it OK. IANAL, tho.

GUI copy mode selection is not scriptable, and verified document authenticity

Posted Jun 2, 2009 6:13 UTC (Tue) by tdwebste (guest, #18154) [Link]

The GUI copy mode selection is not acceptable, because it is not scriptable. What good is a this mode selection if scripts can not be used to open pdfs.

From a practical point of view once I sign a document off I do NOT want others to modify that document without some indication.

I currently use git to sign documents off. This works well for me, but takes a bit of explaining for lawyers understand how and why the document's authenticity is verified.

GUI copy mode selection is not scriptable, and verified document authenticity

Posted Jun 2, 2009 8:10 UTC (Tue) by tzafrir (subscriber, #11501) [Link]

What do you mean by "not scriptable"? Not scriptable by which means?

A shell script that disables it through the configuration, a KDE-level sccript that works through the GUI to disable it, or whatever.

The "DRM" protection is not reliable and enforceable. If you think it is, please point to such an immutable document for the amusement of the crowd.

BTW: I can still generate a new document with your content (give or take a few minor changes) and re-sign it with my signature. The generated document will have a valid format. If that's all you check you won't get very far.

Okular, Debian, and copy restrictions

Posted Jun 3, 2009 5:22 UTC (Wed) by butlerm (subscriber, #13312) [Link]

"Accordingly, the following patents are licensed on a royalty-free,
nonexclusive basis for the term of each patent and for the sole purpose of
developing software that produces, consumes, and interprets *PDF files* that
are compliant with the Specification"

The above quoted paragraph has nothing to do with the issue at hand. It
doesn't say "produces, consumes, and interprets PDF files in a manner
compliant with the Specification. It says "produces, consumes and interprets
PDF *files* that *are* compliant with the Specification". That is a big
difference.

i.e. if your product reads and/or writes spec-compliant PDF files, you are
fine, but if you purposely generate non-conformant "PDF" files you are not.
What you do with the data once you have read it in is not addressed above at
all.

Okular, Debian, and copy restrictions

Posted Jun 4, 2009 7:17 UTC (Thu) by Trelane (subscriber, #56877) [Link]

Very good catch. I totally missed that. The MSFT Office - Adobe kerfluffle makes even more sense now. (Think MSFT-Java and Sun)

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds