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
| ||
|
Date: Sun, 1 Nov 2015 10:07:14 +0100 (CET) From: Jiri Kosina <jikos@...nel.org> To: Chris J Arges <chris.j.arges@...onical.com> cc: Jessica Yu <jeyu@...hat.com>, live-patching@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>, Seth Jennings <sjenning@...hat.com>, Vojtech Pavlik <vojtech@...e.com>, linux-api@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: livepatch: old_name@..._addr scheme in livepatch sysfs directory On Sat, 31 Oct 2015, Chris J Arges wrote: > Makes sense to me. Is there a reason why the sysfs entries are visible > to non-root users? Well, kptr_restrict applies only to values printed using '%pK'. So if the sysfs handler is using other printk() format string to print the pointer, it'll be leaked out (and should eventually be fixed). Thanks, -- Jiri Kosina SUSE Labs -- 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/
Powered by blists - more mailing lists