ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: digital signing in ConTeXt
Date: Tue, 18 Jun 2024 19:28:03 +0200	[thread overview]
Message-ID: <92b5898b-d28d-453e-88d4-a40d0c140d5f@gmx.es> (raw)
In-Reply-To: <1f50da8b-c8d4-4a14-aec6-da3641432afc@freedom.nl>

On 6/18/24 18:42, Hans Hagen via ntg-context wrote:
> On 6/18/2024 6:26 PM, Pablo Rodriguez via ntg-context wrote:
>> [...]
>> As far as I know, this has to be a reason for digest mismatch (or a huge
>> hash collision).
>
> could be (depends on checker) but it we change that we also need to
> change the verify offset (so two patches)

I have just discovered that verify didn’t work with the binary.

Figuring out now how to testing with the library.

>> Signatures in PDF-2.0 loose their possibility of other ranges than the
>> entire file. Their use is simply not allowed.
>
> so more limited then to basically two ranges

It makes sense and it is recommended for PDF-1.x.

>>>> Sorry for insisting, but please don’t require plaintext password in the
>>>> command line (again, OpenSSL prompts for it).
>>> not if we use the library
>>
>> Weird, on both Linux64 and Win64, the openssl runner requires the
>> openssl binary to be installed.
>
> i meant the --library option

In that case, when --library is not invoked, we might avoid mandating
the password in plain text.

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
___________________________________________________________________________________

  reply	other threads:[~2024-06-18 17:28 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
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 [this message]
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=92b5898b-d28d-453e-88d4-a40d0c140d5f@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).