Re: file(1) now with seccomp support enabled

To: debian-devel@lists.debian.org
Subject: Re: file(1) now with seccomp support enabled
From: Vincas Dargis <vindrg@gmail.com>
Date: Fri, 26 Jul 2019 22:47:00 +0300
Message-id: <[🔎] 9aa6c5bf-5a2f-ddf9-3790-7f03c7bf269e@gmail.com>
In-reply-to: <[🔎] 1564156118@msgid.manchmal.in-ulm.de>
References: <[🔎] 1563549514@msgid.manchmal.in-ulm.de> <[🔎] 1564156118@msgid.manchmal.in-ulm.de>

On 2019-07-26 18:59, Christoph Biedl wrote:

tl;dr: The file program in unstable is now built with seccomp support
enabled, expect breakage in some rather uncommon use cases.

Interesting, what are these uncommon use cases? Maybe we could confine it with AppArmor instead,since we have it enabled by default?

Reply to:

Follow-Ups:
- Re: file(1) now with seccomp support enabled
  - From: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>

References:
- file(1) now with seccomp support enabled
  - From: Christoph Biedl <debian-devel@lists.debian.org>
- Re: file(1) now with seccomp support enabled
  - From: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>

Prev by Date: Re: does libmyodbc was removed? ther's will no more mysql odbc packages?
Next by Date: Re: tag2upload (git-debpush) service architecture - draft
Previous by thread: Re: file(1) now with seccomp support enabled
Next by thread: Re: file(1) now with seccomp support enabled
Index(es):
- Date
- Thread