linux-kernel - Re: /proc/timer_list leaks the real pids of the associated processes

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: <alpine.DEB.2.20.1702081045440.3536@nanos>
Date:   Wed, 8 Feb 2017 10:47:23 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Jessica Frazelle <me@...sfraz.com>
cc:     Kees Cook <keescook@...gle.com>, Xing Gao <xgao01@...il.wm.edu>,
        LKML <linux-kernel@...r.kernel.org>,
        "kernel-hardening@...ts.openwall.com" 
        <kernel-hardening@...ts.openwall.com>,
        "Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: /proc/timer_list leaks the real pids of the associated
 processes

On Tue, 7 Feb 2017, Jessica Frazelle wrote:

> So I used to use this "feature" as a hack to see if something was
> running in a k8s cluster or not because fluentd gives a lot of things
> away.

That file does not tell you at all whether something is running or not. It
merily tells you that there are timers queued.

> Runc basically decided to mask this file so it stopped happening
> though. But I think namespace aware is the right decision.

Unless you can come up with a real good argument why this is usefull beyond
debugging and crystal ball hackery, it's going to go away.

Thanks,

	tglx