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: Sun, 21 Feb 2021 10:55:16 +0100 [thread overview]
Message-ID: <CAEwRq=rCopYYM6dbZ=8PkTwEeC4M6_KAyRAzy+qHLjmahOM+qA@mail.gmail.com> (raw)
In-Reply-To: <YDGWiCfiLLAdon6m@jasmine.lan>
Hello,
On Sun, Feb 21, 2021 at 12:09 AM Leo Famulari <leo@famulari.name> wrote:
> I noticed that libwaive hasn't been active in a few years. I wonder if
> it's something we should pursue...
libwaive is a single-file C (~300 LOCs [1]) source code library, I glanced over
it and it looks straightforward enough. I compared it to the seccomp manpage
[2] code samples and saw nothing suspicious.
I think it may not have been updated for newly added syscalls, but that
should not make it unsecure, mainly because what is not explicitely allowed
is prevented from use (default-locked policy [3]).
So, I'll wait for a bit more feedback before working on this, but I think
it may still be a worthwhile addition.
WDYT ?
[1] https://github.com/dimkr/libwaive/blob/master/waive.c
[2] https://man7.org/linux/man-pages/man3/seccomp_rule_add.3.html
[3] https://en.wikipedia.org/wiki/Seccomp
--
Vincent Legoll
next prev parent reply other threads:[~2021-02-21 9:56 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
2021-02-20 21:38 ` Vincent Legoll
2021-02-20 23:08 ` Leo Famulari
2021-02-21 9:55 ` Vincent Legoll [this message]
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=rCopYYM6dbZ=8PkTwEeC4M6_KAyRAzy+qHLjmahOM+qA@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).