mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Kees Cook <keescook@chromium.org>
Cc: Andy Lutomirski <luto@amacapital.net>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Paul Moore <paul@paul-moore.com>,
	Richard Weinberger <richard@nod.at>,
	libseccomp-discuss@lists.sourceforge.net,
	Will Drewry <wad@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: ARM audit, seccomp, etc are broken wrt OABI syscalls
Date: Thu, 7 Nov 2013 17:04:48 -0200	[thread overview]
Message-ID: <20131107190448.GA14011@khazad-dum.debian.net> (raw)
In-Reply-To: <CAGXu5jK6Q_CZTvKo3xT9CEjJ5qyMAP2qHby1YPCg4b72aRUNBg@mail.gmail.com>

On Thu, 07 Nov 2013, Kees Cook wrote:
> On Thu, Nov 7, 2013 at 4:55 AM, Henrique de Moraes Holschuh
> <hmh@hmh.eng.br> wrote:
> > On Tue, 05 Nov 2013, Andy Lutomirski wrote:
> >> Maybe the thing to do is to put a warning in the config text for
> >> CONFIG_OABI_COMPAT that describes the problems (malicious userspace
> >> can confuse syscall auditors, strace, etc.), change the "if in doubt"
> >> part to N, and disable seccomp filters if CONFIG_OABI_COMPAT.  That
> >> might even get Debian to change their default.
> >
> > Bug reported to the Debian BTS: #728975
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728975
> 
> FWIW, Ubuntu has also now disabled OABI_COMPAT going forward:
> https://lists.ubuntu.com/archives/kernel-team/2013-November/034242.html

Unless something very weird happens, it looks like that's also what Debian
will do.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2013-11-07 19:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 22:36 Andy Lutomirski
2013-11-06  0:14 ` Kees Cook
2013-11-06  0:40   ` Russell King - ARM Linux
2013-11-06  3:22     ` Andy Lutomirski
2013-11-07 12:55       ` Henrique de Moraes Holschuh
2013-11-07 17:54         ` Kees Cook
2013-11-07 19:04           ` Henrique de Moraes Holschuh [this message]
2013-11-06  9:52     ` Mikael Pettersson
2013-11-06 22:30   ` Matt Sealey
2013-11-06 22:33     ` Andy Lutomirski
2013-11-06 15:32 ` [libseccomp-discuss] " Eric Paris
2013-11-06 15:51   ` Russell King - ARM Linux
2013-11-06 21:20     ` Will Drewry
2013-11-06 21:26       ` Kees Cook
2013-11-06 21:49         ` Andy Lutomirski
2013-11-06 22:17         ` Russell King - ARM Linux

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131107190448.GA14011@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=keescook@chromium.org \
    --cc=libseccomp-discuss@lists.sourceforge.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=luto@amacapital.net \
    --cc=paul@paul-moore.com \
    --cc=richard@nod.at \
    --cc=wad@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®