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

Holger Levsen holger at layer-acht.org
Fri Jul 26 15:15:17 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.

and, just now, file (1:5.37-5) has been uploaded to Debian unstable with seccomp
re-disabled :/


       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

"... the premise [is] that privacy is about hiding a wrong. It's not.
 Privacy is an inherent human right, and a requirement for maintaining
 the human condition with dignity and respect." (Bruce Schneier)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20190726/bdfe96bd/attachment.sig>

More information about the rb-general mailing list