All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Laura Abbott <labbott@redhat.com>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	"kernel-hardening@lists.openwall.com" 
	<kernel-hardening@lists.openwall.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Kees Cook <keescook@chromium.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Tycho Andersen <tycho@docker.com>,
	"Roberts, William C" <william.c.roberts@intel.com>,
	Tejun Heo <tj@kernel.org>,
	Jordan Glover <Golden_Miller83@protonmail.ch>,
	Greg KH <gregkh@linuxfoundation.org>,
	Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>,
	Ian Campbell <ijc@hellion.org.uk>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <wilal.deacon@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Chris Fries <cfries@google.com>,
	Dave Weinstein <olorin@google.com>,
	Daniel Micay <danielmicay@gmail.com>,
	Djalal Harouni <tixxdz@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>
Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl
Date: Wed, 8 Nov 2017 12:39:41 -0800	[thread overview]
Message-ID: <CA+55aFz6XYtthCgLVJY=985pedeKTwsqPLyL4VVyNpP2TjpPPg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwiaQezaPi2nzmyuFZNgR3PFcsWjjBTHJYBesKrh-Q_pQ@mail.gmail.com>

On Tue, Nov 7, 2017 at 4:59 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> For example, maybe /proc/kallsyms could just default to not showing
> values to non-root users.
>
> Something like the attached TOTALLY UNTESTED patch. It's meant more as
> an RFC, not for application, but it's also meant to show how we can
> tailor the behavior for specific workflow issues.

It seems to work, except I got the condition wrong for
sysctl_perf_event_paranoid.

It should if

        if (sysctl_perf_event_paranoid <= 1)
                return 1;

rather than "<= 0", because '1' still means "allow kernel profiling"
(and the default value is "2").

But I don't know if there is anything else than the profiling code
that _really_ wants access to /proc/kallsyms in user space as a
regular user.

That said, that patch also fixes the /proc/kallsyms root check, in
that now you can do:

    sudo head < /proc/kallsyms

and it still shows all zeroes - because the file was *opened* as a
normal user. That's how UNIX file access security works, and how it is
fundamentally supposed to work (ie passing a file descriptor to a sui
program doesn't magically make it gain privileges).

Anyway, I'm obviously not going to commit that patch now, but I'd be
happy to try it for the 4.15 merge window, to see if we can close
/proc/kallsyms without people screaming..

            Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Laura Abbott <labbott@redhat.com>
Cc: "Tobin C. Harding" <me@tobin.cc>,
	"kernel-hardening@lists.openwall.com"
	<kernel-hardening@lists.openwall.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Kees Cook <keescook@chromium.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Tycho Andersen <tycho@docker.com>,
	"Roberts, William C" <william.c.roberts@intel.com>,
	Tejun Heo <tj@kernel.org>,
	Jordan Glover <Golden_Miller83@protonmail.ch>,
	Greg KH <gregkh@linuxfoundation.org>,
	Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>,
	Ian Campbell <ijc@hellion.org.uk>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <wilal.deacon@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Chris Fries <cfries@google.com>,
Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl
Date: Wed, 8 Nov 2017 12:39:41 -0800	[thread overview]
Message-ID: <CA+55aFz6XYtthCgLVJY=985pedeKTwsqPLyL4VVyNpP2TjpPPg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwiaQezaPi2nzmyuFZNgR3PFcsWjjBTHJYBesKrh-Q_pQ@mail.gmail.com>

On Tue, Nov 7, 2017 at 4:59 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> For example, maybe /proc/kallsyms could just default to not showing
> values to non-root users.
>
> Something like the attached TOTALLY UNTESTED patch. It's meant more as
> an RFC, not for application, but it's also meant to show how we can
> tailor the behavior for specific workflow issues.

It seems to work, except I got the condition wrong for
sysctl_perf_event_paranoid.

It should if

        if (sysctl_perf_event_paranoid <= 1)
                return 1;

rather than "<= 0", because '1' still means "allow kernel profiling"
(and the default value is "2").

But I don't know if there is anything else than the profiling code
that _really_ wants access to /proc/kallsyms in user space as a
regular user.

That said, that patch also fixes the /proc/kallsyms root check, in
that now you can do:

    sudo head < /proc/kallsyms

and it still shows all zeroes - because the file was *opened* as a
normal user. That's how UNIX file access security works, and how it is
fundamentally supposed to work (ie passing a file descriptor to a sui
program doesn't magically make it gain privileges).

Anyway, I'm obviously not going to commit that patch now, but I'd be
happy to try it for the 4.15 merge window, to see if we can close
/proc/kallsyms without people screaming..

            Linus

  reply	other threads:[~2017-11-08 20:39 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 10:32 [PATCH v4] scripts: add leaking_addresses.pl Tobin C. Harding
2017-11-07 10:32 ` [kernel-hardening] " Tobin C. Harding
2017-11-07 10:32 ` Tobin C. Harding
2017-11-07 10:50 ` Greg KH
2017-11-07 10:50   ` [kernel-hardening] " Greg KH
2017-11-07 10:50   ` Greg KH
2017-11-07 20:51   ` Tobin C. Harding
2017-11-07 20:51     ` [kernel-hardening] " Tobin C. Harding
2017-11-07 20:51     ` Tobin C. Harding
2017-11-07 13:56 ` David Laight
2017-11-07 13:56   ` [kernel-hardening] " David Laight
2017-11-07 13:56   ` David Laight
2017-11-07 20:58   ` Tobin C. Harding
2017-11-07 20:58     ` [kernel-hardening] " Tobin C. Harding
2017-11-07 20:58     ` Tobin C. Harding
2017-11-07 21:11     ` Linus Torvalds
2017-11-07 21:11       ` [kernel-hardening] " Linus Torvalds
2017-11-07 21:11       ` Linus Torvalds
2017-11-07 15:51 ` Petr Mladek
2017-11-07 15:51   ` [kernel-hardening] " Petr Mladek
2017-11-07 15:51   ` Petr Mladek
2017-11-07 20:39   ` Tobin C. Harding
2017-11-07 20:39     ` [kernel-hardening] " Tobin C. Harding
2017-11-07 20:39     ` Tobin C. Harding
2017-11-07 23:36 ` [kernel-hardening] " Laura Abbott
2017-11-07 23:36   ` Laura Abbott
2017-11-08  0:59   ` Linus Torvalds
2017-11-08  0:59     ` Linus Torvalds
2017-11-08  0:59     ` Linus Torvalds
2017-11-08 20:39     ` Linus Torvalds [this message]
2017-11-08 20:39       ` Linus Torvalds
2017-11-08 20:39       ` Linus Torvalds
2017-11-09  4:43       ` Kaiwan N Billimoria
2017-11-09  4:43         ` Kaiwan N Billimoria
2017-11-09  4:43         ` Kaiwan N Billimoria
2017-11-09  4:54         ` Kaiwan N Billimoria
2017-11-09  4:54           ` Kaiwan N Billimoria
2017-11-09  4:54           ` Kaiwan N Billimoria
2017-11-09 18:11           ` Steven Rostedt
2017-11-09 18:11             ` Steven Rostedt
2017-11-09 18:11             ` Steven Rostedt
2017-11-10  3:03             ` Kaiwan N Billimoria
2017-11-10  3:03               ` Kaiwan N Billimoria
2017-11-10  3:03               ` Kaiwan N Billimoria
2017-11-08  1:13   ` Tobin C. Harding
2017-11-08  1:13     ` Tobin C. Harding
2017-11-08 12:10 ` [kernel-hardening] " Michael Ellerman
2017-11-08 12:10   ` Michael Ellerman
2017-11-08 12:10   ` Michael Ellerman
2017-11-08 21:16   ` Tobin C. Harding
2017-11-08 21:16     ` Tobin C. Harding
2017-11-08 22:48   ` Tobin C. Harding
2017-11-08 22:48     ` Tobin C. Harding
2017-11-09  0:49     ` Michael Ellerman
2017-11-09  0:49       ` Michael Ellerman
2017-11-09  0:49       ` Michael Ellerman
2017-11-09  2:08       ` Tobin C. Harding
2017-11-09  2:08         ` Tobin C. Harding
2017-11-10 22:12   ` [kernel-hardening] " Frank Rowand
2017-11-10 22:12     ` Frank Rowand
2017-11-12 11:49     ` Michael Ellerman
2017-11-12 11:49       ` Michael Ellerman
2017-11-12 11:49       ` Michael Ellerman
2017-11-12 18:02       ` Frank Rowand
2017-11-12 18:02         ` Frank Rowand
2017-11-12 21:18         ` Tobin C. Harding
2017-11-12 21:18           ` Tobin C. Harding
2017-11-13  1:06         ` Michael Ellerman
2017-11-13  1:06           ` Michael Ellerman
2017-11-13  1:06           ` Michael Ellerman
2017-11-10 13:56 ` kaiwan.billimoria
2017-11-10 13:56   ` kaiwan.billimoria
2017-11-12 22:21   ` Tobin C. Harding
2017-11-12 22:21     ` Tobin C. Harding
2017-11-13  5:46     ` kaiwan.billimoria
2017-11-13  5:46       ` kaiwan.billimoria
2017-11-13  6:08       ` Tobin C. Harding
2017-11-13  6:08         ` Tobin C. Harding
2017-11-13  6:52         ` Kaiwan N Billimoria
2017-11-13  6:52           ` Kaiwan N Billimoria
2017-11-20 15:39       ` [kernel-hardening] " Petr Mladek
2017-11-20 15:39         ` Petr Mladek
2017-11-19 23:56   ` [kernel-hardening] " Tobin C. Harding
2017-11-19 23:56     ` Tobin C. Harding
2017-11-11 23:10 ` Kirill A. Shutemov
2017-11-11 23:10   ` [kernel-hardening] " Kirill A. Shutemov
2017-11-11 23:10   ` Kirill A. Shutemov
2017-11-12 23:06   ` Tobin C. Harding
2017-11-12 23:06     ` [kernel-hardening] " Tobin C. Harding
2017-11-12 23:06     ` Tobin C. Harding
2017-11-13  3:37     ` Kirill A. Shutemov
2017-11-13  3:37       ` [kernel-hardening] " Kirill A. Shutemov
2017-11-13  3:37       ` Kirill A. Shutemov
2017-11-13  4:35       ` Tobin C. Harding
2017-11-13  4:35         ` [kernel-hardening] " Tobin C. Harding
2017-11-13  4:35         ` Tobin C. Harding
2017-11-13  5:27         ` [kernel-hardening] " Kaiwan N Billimoria
2017-11-13  5:27           ` Kaiwan N Billimoria

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='CA+55aFz6XYtthCgLVJY=985pedeKTwsqPLyL4VVyNpP2TjpPPg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=Golden_Miller83@protonmail.ch \
    --cc=Jason@zx2c4.com \
    --cc=catalin.marinas@arm.com \
    --cc=cfries@google.com \
    --cc=danielmicay@gmail.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=ijc@hellion.org.uk \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=netdev@vger.kernel.org \
    --cc=olorin@google.com \
    --cc=pbonzini@redhat.com \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tixxdz@gmail.com \
    --cc=tj@kernel.org \
    --cc=tycho@docker.com \
    --cc=tytso@mit.edu \
    --cc=wilal.deacon@arm.com \
    --cc=william.c.roberts@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.