On Thu, Feb 20, 2020 at 05:40:51PM +0100, Marc Haber wrote:
> So, at the moment, seccomp in apt in stable is unuseable with a more
> recent kernel because of this, and should be switched off on my affected
> systems?
No comments here?
Greetings
Marc
--
--
On Thu, Feb 20, 2020 at 05:21:31PM +0100, Julian Andres Klode wrote:
> It is the correct syntax. libseccomp2 in stable is too old to know
> the new syscalls, and there's no way to override by syscall number in
> apt. Both should be fixed IMO:
>
> - the list of syscalls the libseccomp library handl
Control: clone -1 -2
Control: reassign -2 libseccomp/2.3.3-4
Control: retitle -1 apt: allow seccomp overrides by number
Control: retitle -2 libseccomp: syscalls missing in stable
On Thu, Feb 20, 2020 at 05:00:18PM +0100, Marc Haber wrote:
> Package: apt
> Version: 1.8.2
> Severity: normal
>
> Hi,
Package: apt
Version: 1.8.2
Severity: normal
Hi,
/usr/share/doc/apt/examples/configure-index.gz says:
APT::Sandbox
{
User "";
ResetEnvironment "";
Verify ""
{
Groups "";
IDs "";
Regain "";
};
seccomp ""
{
print ""; // print what syscall was trapped
4 matches
Mail list logo
