From: Henning Hraban Ramm <texml@fiee.net>
To: ntg-context@ntg.nl
Subject: [NTG-context] Re: digital signing in ConTeXt
Date: Mon, 17 Jun 2024 20:21:46 +0200 [thread overview]
Message-ID: <337e1c35-86f1-47d9-b6ba-e6640c816875@fiee.net> (raw)
In-Reply-To: <56e22216-05a2-4f33-849f-c3aff7ab9946@gmx.es>
Am 17.06.24 um 19:51 schrieb Pablo Rodriguez via ntg-context:
> Dear list,
>
> the latest version of LMTX can digitally sign PDF documents. It requires
> OpenSSL installed (since it does the crypto part).
>
> Could anyone confirm the following issues?
>
> 1. The signature I get is wrong, unless I apply this patch
> (https://mailman.ntg.nl/archives/list/dev-context@ntg.nl/message/T3OCKVZWTUTIXCSOKIFRVJ4X76MROZHE/attachment/3/byterange.diff
> [sent by myself to the devel list]).
Can confirm.
Before patching, I checked with …
– Acrobat Reader: doesn’t recognize a signature
– Foxit Reader: "a signature is invalid"
> 2. I cannot get any signature display in Acrobat. Does any PDF viewer (I
> have tested this with pdfsig from poppler and MuPDF-GL) display the
> digital signature at all?
After patching, I checked with …
– Acrobat Reader: doesn’t recognize a signature
– Foxit Reader: "there’s something wrong with a signature" (i.e.
different message)
– Apple Preview: doesn’t handle signatures at all
– PDF Studio Pro 2023: shows signature, "don’t know if valid, issuer
unknown" etc.
– Master PDF Editor: can edit form fields, but doesn’t handle signatures
– Skim: doesn’t handle signatures
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2024-06-17 18:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 17:51 [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-17 18:21 ` Henning Hraban Ramm [this message]
2024-06-17 18:36 ` [NTG-context] " Pablo Rodriguez via ntg-context
2024-06-17 22:52 ` Hans Hagen via ntg-context
2024-06-18 6:44 ` Pablo Rodriguez via ntg-context
2024-06-18 8:27 ` Hans Hagen via ntg-context
2024-06-18 16:26 ` Pablo Rodriguez via ntg-context
2024-06-18 16:42 ` Hans Hagen via ntg-context
2024-06-18 17:28 ` Pablo Rodriguez via ntg-context
2024-06-18 17:42 ` Pablo Rodriguez via ntg-context
2024-06-19 7:28 ` Hans Hagen via ntg-context
2024-06-19 16:59 ` Pablo Rodriguez via ntg-context
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=337e1c35-86f1-47d9-b6ba-e6640c816875@fiee.net \
--to=texml@fiee.net \
--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).