[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#45344] [Patch 0/2] Libwaive for signify
From: |
Leo Famulari |
Subject: |
[bug#45344] [Patch 0/2] Libwaive for signify |
Date: |
Sun, 21 Feb 2021 14:04:04 -0500 |
On Sun, Feb 21, 2021 at 10:55:16AM +0100, Vincent Legoll wrote:
> 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 ?
I think you've done all the things a reviewer would ask for, so please
proceed as you see fit :)