linux-kernel - Re: [PATCH 0/5] RFC: Public key encryption of dmesg by the kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180118215755.GB17196@amd>
Date:   Thu, 18 Jan 2018 22:57:55 +0100
From:   Pavel Machek <pavel@....cz>
To:     Dan Aloni <dan@...nelim.com>
Cc:     linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com
Subject: Re: [PATCH 0/5] RFC: Public key encryption of dmesg by the kernel

On Sat 2017-12-30 19:57:59, Dan Aloni wrote:
> From: Dan Aloni <dan@...nelim.com>
> 
> Hi All,
> 
> There has been a lot of progress in recent times regarding the removal
> of sensitive information from dmesg (pointers, etc.), so I figured - why
> not encrypt it all? However, I have not found any existing discussions
> or references regarding this technical direction.
> 
> 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.

Yes, we have "TiVo" problem in mobile space, but please no, don't make
it worse.

We should not make it easy for device makers to lock devices down from
their owners.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)