linux-kernel - Re: [PATCH -repost 05/21] kgr: update Kconfig documentation

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20140627191845.GA1408@xo-6d-61-c0.localdomain>
Date:	Fri, 27 Jun 2014 21:18:45 +0200
From:	Pavel Machek <pavel@....cz>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Jiri Slaby <jslaby@...e.cz>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org, tj@...nel.org, rostedt@...dmis.org,
	mingo@...hat.com, akpm@...ux-foundation.org, andi@...stfloor.org,
	paulmck@...ux.vnet.ibm.com, jirislaby@...il.com,
	Vojtech Pavlik <vojtech@...e.cz>, Michael Matz <matz@...e.de>,
	Udo Seidel <udoseidel@....de>
Subject: Re: [PATCH -repost 05/21] kgr: update Kconfig documentation

Hi!

> > This now writes:
> > +       help
> > +         Select this to enable kGraft online kernel patching. The
> > +         runtime price is nearly zero, so it is safe to say Y here
> > +         provided you are aware of all the consequences (e.g. in
> > +         security).
> > 
> > Is it OK with you?
> 
> This might cause a false impression that we are actually opening a 
> security hole into a system, which is not true at all.
> 
> Yes, backdoor writeres might (or might not) make use of kGraft API, but 
> they have gazillion of other comparable options (*probes, ftrace, 
> text_poke(), ...).
> 
> I'd perhaps propose something like
> 
> "Select this to enable kGraft live kernel patching. The runtime penalty is 
> nearly zero, so it is safe to say Y here if you want the kernel to expose 
> API for live patching to modules".

Well. People that are not distro vendors will not prepare patches for
themselves, right? And patches prepared for suse will not work on
self-configured kernels.

So probably everyone should say "N" here...


                                           				Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/