Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 16 Jan 2018 11:09:43 +0900
From: Sergey Senozhatsky <>
To: Steven Rostedt <>
Cc: Dan Aloni <>,
	Sergey Senozhatsky <>,,,
	Petr Mladek <>,
	Linus Torvalds <>,
	Peter Zijlstra <>,
	Andrew Morton <>,
	Kees Cook <>
Subject: Re: [PATCHv2 5/7] printk: allow kmsg to be encrypted using public
 key encryption

On (01/15/18 07:52), Steven Rostedt wrote:
> I'm very skeptical that such an approach has much benefit. From the
> email referenced above:

agreed. dmesg can be SECURITY_DMESG_RESTRICT.
so the patch is *probably* aiming the systems in which anyone can read
dmesg, but we kinda don't want that to happen. may be I'm missing the

> > I am not sure that desktop and power users would like to have their
> > kernel message encrypted, but there are scenarios such as in mobile
> > devices, where only the developers, makers of devices, may actually
> > benefit from access to kernel prints messages, and the users may be
> > more protected from exploits.
> Do you have any backing from makers of such devices? I'd like to hear
> from Google's Android team or whoever that would turn this feature on.
> I would be hard pressed to add such a feature if it's never used.



Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.