Re: file(1) now with seccomp support enabled

To: debian-devel@lists.debian.org
Subject: Re: file(1) now with seccomp support enabled
From: Jakub Wilk <jwilk@jwilk.net>
Date: Sat, 27 Jul 2019 09:42:43 +0200
Message-id: <[🔎] 20190727074243.tz5whwsqxl7eb7b6@jwilk.net>
Mail-followup-to: debian-devel@lists.debian.org
In-reply-to: <[🔎] 1564191466@msgid.manchmal.in-ulm.de>
References: <[🔎] 1563549514@msgid.manchmal.in-ulm.de> <[🔎] 1564156118@msgid.manchmal.in-ulm.de> <[🔎] 9aa6c5bf-5a2f-ddf9-3790-7f03c7bf269e@gmail.com> <[🔎] 1564191466@msgid.manchmal.in-ulm.de>

* Christoph Biedl <debian.axhn@manchmal.in-ulm.de>, 2019-07-27, 03:55:

The file program should[citation needed] not write to any file


...except when using the -C option.

--
Jakub Wilk

Reply to:

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>
- Re: file(1) now with seccomp support enabled
  - From: Vincas Dargis <vindrg@gmail.com>
- Re: file(1) now with seccomp support enabled
  - From: Christoph Biedl <debian.axhn@manchmal.in-ulm.de>

Prev by Date: Re: file(1) now with seccomp support enabled
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