From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 45344@debbugs.gnu.org
Subject: [bug#45344] [Patch 0/2] Libwaive for signify
Date: Sat, 20 Feb 2021 13:46:38 -0500 [thread overview]
Message-ID: <YDFZDvm6svVOtI0Q@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=pBWFuJw+FoKCQ3amdRdm1c2+s1wzMEzmGgu-exOS=Qrg@mail.gmail.com>
On Sun, Dec 20, 2020 at 07:49:22PM +0100, Vincent Legoll wrote:
> The following series adds libwaive, use it
> for signify, and remove the TODO item.
>
> I don't know if the test I did is sufficient to
> ensure that the libwaive was used but the
> following worked OK:
>
> wget https://ftp.openbsd.org/pub/OpenBSD/6.8/openbsd-68-base.pub
> wget https://cdn.openbsd.org/pub/OpenBSD/6.8/amd64/miniroot68.img
> wget https://cdn.openbsd.org/pub/OpenBSD/6.8/amd64/SHA256
> sha256sum -c --ignore-missing SHA256
> wget https://cdn.openbsd.org/pub/OpenBSD/6.8/amd64/SHA256.sig
> signify -Cp ./openbsd-68-base.pub -x SHA256.sig miniroot68.img
Well, as long as signify keeps working, these extra security features
are offered as "best effort" on Linux. From what I can see, the only
OpenBSD software that is fully supported on Linux is OpenSSH. So, we are
only missing the description and synopsis.
next prev parent reply other threads:[~2021-02-20 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 18:49 [bug#45344] [Patch 0/2] Libwaive for signify Vincent Legoll
2020-12-20 18:53 ` [bug#45344] [PATCH 1/2] gnu: Add libwaive Vincent Legoll
2020-12-20 18:53 ` [bug#45344] [PATCH 2/2] gnu: signify: Build with libwaive to emulate OpenBSD's pledge() Vincent Legoll
2020-12-20 18:55 ` [bug#45344] Following up Vincent Legoll
2021-02-20 18:46 ` Leo Famulari [this message]
2021-02-20 19:05 ` [bug#45344] [Patch 0/2] Libwaive for signify Vincent Legoll
2021-02-20 21:38 ` Vincent Legoll
2021-02-20 23:08 ` Leo Famulari
2021-02-21 9:55 ` Vincent Legoll
2021-02-21 19:04 ` Leo Famulari
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=YDFZDvm6svVOtI0Q@jasmine.lan \
--to=leo@famulari.name \
--cc=45344@debbugs.gnu.org \
--cc=vincent.legoll@gmail.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/guix.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.