ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ConTeXt users <ntg-context@ntg.nl>
Subject: digitally sign fields with MuPDF-GL
Date: Thu, 13 Jul 2023 20:23:01 +0200	[thread overview]
Message-ID: <cfef9220-c349-e679-e415-ef69b2735571@gmx.es> (raw)

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

Dear list,

having the following sample code:

  \setuppapersize[A4, landscape]
  \setuplayout[page]
  \setupinteraction[state=start]
  \starttext
  \setupfield[sl][horizontal]
    [frame=off, width=\textwidth, height=\textheight]
  \definefield[x][signature][sl]
  \field[x]

I also attach a sample certificate with password ABCabc.

The binaries for Windows provided by Artifex do not provide SSL support.
I’m on Linux myself, and something like MSYS2 provides binaries with
support for Linux (https://packages.msys2.org/base/mingw-w64-mupdf). I
wonder whether Homebrew provides mupdf-gl (I cannot say from
https://formulae.brew.sh/formula/mupdf).

If I try to sign the output PDF with the previous password, using
mupdf-gl or "mutool sign" (version 1.2.2), the signature annotation is
only viewed by MuPDF, MuPDF-GL and SumatraPDF.

On Linux, neither Evince or xpdf can display the signature annotation.

On Windows, Acrobat Reader DC doesn’t display the signature annotation,
nor it shows any info about the document being signed (BTW, I used
another certificate for this).

If I open the unsigned document with Acrobat Reader DC and save it, then
mupdf-gl can sign the saved document that Acrobat can handle (both
annotation and signature info) and Evince and xpdf can display the
signature.

I guess what might be causing this issue and I’m investigating it.

But it would really help, if someone can confirm the issue with MuPDF-GL
(or "mutool sign") and Acrobat (Reader or not).

Many thanks for your help,

Pablo

[-- Attachment #2: mycert.pfx --]
[-- Type: application/x-pkcs12, Size: 2736 bytes --]

[-- Attachment #3: Type: text/plain, Size: 495 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

                 reply	other threads:[~2023-07-13 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cfef9220-c349-e679-e415-ef69b2735571@gmx.es \
    --to=oinos@gmx.es \
    --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).