From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: digital signing in ConTeXt
Date: Mon, 17 Jun 2024 20:36:40 +0200 [thread overview]
Message-ID: <2f1406af-71fe-425d-aee3-c9aeeca76be7@gmx.es> (raw)
In-Reply-To: <337e1c35-86f1-47d9-b6ba-e6640c816875@fiee.net>
On 6/17/24 20:21, Henning Hraban Ramm wrote:
>> [...]
> Can confirm.
Many thanks for your testing, Hraban.
> Before patching, I checked with …
> – Acrobat Reader: doesn’t recognize a signature
> – Foxit Reader: "a signature is invalid"
The signature is invalid since it leaves an space outside the signing range.
> 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)
The certificate is self-signed. Its validity (not the correctness of the
signature) is problematic to say the least.
> – PDF Studio Pro 2023: shows signature, "don’t know if valid, issuer
> unknown" etc.
Again, as a certificate, this is a crappy.
But this detects document modifications after being signed.
Just in case Hans reads the message:
It would be great that OpenSSL asks for the password directly.
This is a basic security issue, not to leave plain-text passwords on the
terminal.
Many thanks for your help,
Pablo
___________________________________________________________________________________
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:37 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 ` [NTG-context] " Henning Hraban Ramm
2024-06-17 18:36 ` Pablo Rodriguez via ntg-context [this message]
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=2f1406af-71fe-425d-aee3-c9aeeca76be7@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).