From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Subject: Re: PDF Digital Signatures
Date: Mon, 19 Mar 2012 23:12:29 +0100 [thread overview]
Message-ID: <4F67AF4D.9030709@wxs.nl> (raw)
In-Reply-To: <CALBOmsZ_EJwtazugcdzpUW+pQ8L9z9Qs4njADXfiBOAbi1YCDA@mail.gmail.com>
On 19-3-2012 22:08, Mojca Miklavec wrote:
> On Mon, Mar 19, 2012 at 17:51, luigi scarso wrote:
>>
>>> I'm not sure about it, but I'm tempted to believe that digitally
>>> signing PDFs might be one of "forbidden" functionality that requires
>>> you to buy a licence for Acrobat.
>> Why ? As long it is described in the ISO standard, it can be
>> implemented in mkiv (easily is another question).
>
> As I said: I'm not sure whether or not it is legal to implement it or not.
>
> There seem to be two separate issues:
> (a) creating a document that others users will be able to fill in and sign
> (b) signing your own document
> Martin usually knows the legal issues better. I'm not sure about the
> exact legal state and I'm not sure where to check it without getting
> lost in "hundreds" of pages of EULA or other documents, but (b) is
> described in PDF Reference Manual
> (http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_2008.pdf)
> in Chapter 12 and cannot be any more complicated to implement than all
> other PDF features that Hans, Taco or Hartmut ever implemented.
sure, it's just that I never needed something like that
> Out of curiosity: is inability to create password-protected PDF files
> with pdfTeX/LuaTeX due to legal issues or due to nobody caring enough
> to implement it?
it's not worth the trouble. Afaik it's a second pass issue and would
complicate the code much.
Just use qpdf to do it ... pretty fast.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-03-19 22:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 9:27 Andreas Schneider
2012-03-19 15:41 ` Mojca Miklavec
2012-03-19 16:28 ` Andreas Schneider
2012-03-19 16:51 ` luigi scarso
2012-03-19 21:08 ` Mojca Miklavec
2012-03-19 22:12 ` Hans Hagen [this message]
2012-03-20 19:23 ` Mojca Miklavec
2012-03-20 19:27 ` Hans Hagen
2012-03-20 21:25 ` Michael Hallgren
2012-03-20 22:37 ` Martin Schröder
2012-03-19 21:30 ` Hans Hagen
2012-03-19 18:53 ` Kip Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F67AF4D.9030709@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).