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

Eli Schwartz eschwartz at archlinux.org
Fri Jul 26 15:47:01 UTC 2019

On 7/26/19 11:15 AM, Holger Levsen wrote:
> 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.
> and, just now, file (1:5.37-5) has been uploaded to Debian unstable with seccomp
> re-disabled :/

Well, FWIW I've since noticed that 5.38 will have support for -S as a
no-op even when seccomp is disabled... so it can be reliably suppressed
by programs that are incompatible with the sandbox.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1601 bytes
Desc: OpenPGP digital signature
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20190726/97cd56c8/attachment.sig>

More information about the rb-general mailing list