[rb-general] file(1) now with seccomp support enabled

David A. Wheeler dwheeler at dwheeler.com
Fri Jul 26 19:56:07 UTC 2019

> On Mon, Jul 22, 2019 at 05:55:43PM -0400, Eli Schwartz wrote:
> > Over in Arch Linux we have opted instead to disable seccomp in file(1)
> > entirely -- it completely breaks common workflows that require looking at
> > files, and there's no way an application can actually know how to make it
> > work.

On Fri, 26 Jul 2019 15:15:17 +0000, Holger Levsen <holger at layer-acht.org> wrote:
> and, just now, file (1:5.37-5) has been uploaded to Debian unstable with seccomp
> re-disabled :/

Can you point me to a discussion of the common workflows this breaks? (URL wanted).
This seems unfortunate... and maybe it's fixable long-term.

--- David A. Wheeler

More information about the rb-general mailing list