From: Andreas Enge <andreas@enge.fr>
To: Timotej Lazar <timotej.lazar@araneo.si>
Cc: 62878@debbugs.gnu.org
Subject: [bug#62878] [PATCH core-updates] gnu: openhsm: Fix test failure with openssl-3.
Date: Mon, 17 Apr 2023 11:18:16 +0200 [thread overview]
Message-ID: <ZD0O2I/UQ66VHX3x@jurong> (raw)
In-Reply-To: <20230416084557.22419-1-timotej.lazar@araneo.si>
Hello Timotej,
Am Sun, Apr 16, 2023 at 10:45:57AM +0200 schrieb Timotej Lazar:
> * gnu/packages/patches/softhsm-fix-openssl3-tests.patch: Add patch from
> Debian.
> * gnu/packages/security-token.scm (softhsm): Use it.
> * gnu/local.mk (dist_patch_DATA): Register it.
thanks for your patch! Since this is security related, I would like to dig
a bit deeper. That the package itself has a wrong homepage (maybe we could
switch to https://www.opendnssec.org/softhsm/ at the same occasion?) does
not help, nor that the software looks abandoned (last commit on
https://github.com/opendnssec/SoftHSMv2 about a year ago, last release
three years ago). But as I understand it, it is more of educational use
than to provide actual security?
Could you add a pointer to the source of the patch (at the top of the file,
for instance)? I did not find it in the Debian package. And maybe add a
copyright line for yourself.
Andreas
next prev parent reply other threads:[~2023-04-17 9:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 8:45 [bug#62878] [PATCH core-updates] gnu: openhsm: Fix test failure with openssl-3 Timotej Lazar
2023-04-17 9:18 ` Andreas Enge [this message]
2023-04-17 20:15 ` Timotej Lazar
2023-04-17 20:18 ` [bug#62913] [PATCH core-updates v2] " Timotej Lazar
[not found] ` <handler.62913.B.16817627115691.ack@debbugs.gnu.org>
2023-04-17 21:10 ` [bug#62913] Acknowledgement ([PATCH core-updates v2] gnu: openhsm: Fix test failure with openssl-3.) Timotej Lazar
2023-04-18 20:05 ` [bug#62913] [PATCH core-updates] gnu: openhsm: Fix test failure with openssl-3 Andreas Enge
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZD0O2I/UQ66VHX3x@jurong \
--to=andreas@enge.fr \
--cc=62878@debbugs.gnu.org \
--cc=timotej.lazar@araneo.si \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).