From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [suspend] [patch 3/3] attach-fail-reasons: SELinux deny_ptrace
Date: Thu, 08 Mar 2012 16:46:00 -0000 [thread overview]
Message-ID: <20120308164622.GA29697@host2.jankratochvil.net> (raw)
In-Reply-To: <87d38nnivc.fsf@fleche.redhat.com>
On Thu, 08 Mar 2012 17:43:35 +0100, Tom Tromey wrote:
> I wonder whether ptrace-hardening approaches other than SELinux still
> have restrictions on PTRACE_TRACEME. If so then you may want a similar
> patch anyhow.
There is a note that YAMA does not restrict PTRACE_TRACEME, like I recommended
for SELinux 'deny_ptrace':
https://bugzilla.redhat.com/show_bug.cgi?id=786878#c17
While it is good to handle errors from system calls I am not sure it is worth
to complicate GDB this way for a case which does not happen in real world.
Regards,
Jan
next prev parent reply other threads:[~2012-03-08 16:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 6:18 Jan Kratochvil
2012-03-06 8:35 ` Mark Kettenis
2012-03-06 8:42 ` Jan Kratochvil
2012-03-06 19:29 ` Tom Tromey
2012-03-08 6:53 ` [suspend] " Jan Kratochvil
2012-03-08 16:43 ` Tom Tromey
2012-03-08 16:46 ` Jan Kratochvil [this message]
2012-03-08 17:50 ` Tom Tromey
2012-03-08 16:51 ` Pedro Alves
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=20120308164622.GA29697@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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