unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 45344@debbugs.gnu.org
Subject: [bug#45344] [Patch 0/2] Libwaive for signify
Date: Sat, 20 Feb 2021 20:05:54 +0100	[thread overview]
Message-ID: <CAEwRq=ojf6PA1Vn8LCaOnTBLypsEU8_9dFDEgc_gtJvuS3PEVg@mail.gmail.com> (raw)
In-Reply-To: <YDFZDvm6svVOtI0Q@jasmine.lan>

Hello,

On Sat, Feb 20, 2021 at 7:46 PM Leo Famulari <leo@famulari.name> wrote:
> 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.

Yes, I'm not knowledgeable enough to check for sure that this is really
enhancing security or anything else, but saw the light^Wcomment and
tried to do it... It certainly is more interesting than bare boring package
version updates (which I'll still continue to do anyways though).

I'll update the patch with desc and synopsis.

Thanks

--
Vincent Legoll




  reply	other threads:[~2021-02-20 19:07 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 ` [bug#45344] [Patch 0/2] Libwaive for signify Leo Famulari
2021-02-20 19:05   ` Vincent Legoll [this message]
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

  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='CAEwRq=ojf6PA1Vn8LCaOnTBLypsEU8_9dFDEgc_gtJvuS3PEVg@mail.gmail.com' \
    --to=vincent.legoll@gmail.com \
    --cc=45344@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).