all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marc Baaden <baaden@smplinux.de>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: 68373@debbugs.gnu.org
Subject: bug#68373: 29.1; Bug in MH-E's support for using openssl to generate the checksum
Date: Mon, 15 Jan 2024 00:00:22 +0100	[thread overview]
Message-ID: <69285.1705273222@lux.lbt.ibpc.fr> (raw)
In-Reply-To: <26781.1705271920@alto>

Hi Mike,

Sure. Concerning MacOS, actually now I am on 12 because when my new
harddisk replacement (sort of memory stick) arrived, it was not
recognized by OS Catalina v10 and I was forced to upgrade. I hope this
will not mess up the bug follow-up.

I used your email text file for this test.

:541; openssl version
OpenSSL 3.1.2 1 Aug 2023 (Library: OpenSSL 3.1.2 1 Aug 2023)

:542; openssl md5 BU/6
MD5(BU/6)= f4aa56ee20c406082d260b0b3b0e3ca1

Let me know if you need anything else,
Kind regards,
Marc

Mike Kupfer <kupfer@rawbw.com> wrote:

> MH-E will look for md5sum, openssl, and md5, in that order.  The first
> one that it finds will be used.  So with just openssl and md5 installed,
> MH-E will use openssl.
> 
> Given that we are working with MacOS 10, I wonder if there is some
> incompatibility between MH-E and the openssl that is installed.  This
> could be in the command-line syntax or in the format of the output.
> 
> Marc, could you find a text file, run the following 2 commands, and then
> reply with the output from the commands?
> 
>   openssl version
> 
>   openssl md5 <path_to_text_file>
> 
> thanks,
> mike
> 





  reply	other threads:[~2024-01-14 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 17:34 bug#68373: 29.1; Bug in MH-E's support for using openssl to generate the checksum Marc Baaden
2024-01-14 22:38 ` Mike Kupfer
2024-01-14 23:00   ` Marc Baaden [this message]
2024-01-14 23:58     ` Mike Kupfer
2024-01-17 18:54       ` Marc Baaden
2024-01-19 13:18   ` Marc Baaden
2024-01-20  2:22     ` Mike Kupfer

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=69285.1705273222@lux.lbt.ibpc.fr \
    --to=baaden@smplinux.de \
    --cc=68373@debbugs.gnu.org \
    --cc=kupfer@rawbw.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.