linux-kernel - firmware: dmi-sysfs: why is the access mode of dmi sysfs entries restricted to 0400?

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-next>] [day] [month] [year] [list]

Date:   Wed, 4 Dec 2019 15:31:22 +0800
From:   Guoheyi <guoheyi@...wei.com>
To:     Mike Waychison <mikew@...gle.com>
CC:     <linux-kernel@...r.kernel.org>,
        wanghaibin 00208455 <wanghaibin.wang@...wei.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Subject: firmware: dmi-sysfs: why is the access mode of dmi sysfs entries
 restricted to 0400?

Hi,

Why is the access mode of dmi sysfs entries restricted to 0400? Is it 
for security concern? If it is, which information do we consider as privacy?

We would like to fetch CPU information from non-root application, is 
there feasible way to do that?

Any advice is appreciated.

Thanks,

Heyi