As I stated early in the email thread, mdesc sysfs module has the same
permissions as /dev/mdesc chardev. So if you're happy with /dev/mdesc
being root, then you're also happy with mdesc sysfs expsing the same data
with the same perimssions and I don't understand that fuss around the audit.
Please elaborate as I don't understand what's happening here. Thank you.
Eric Saint-Etienne - Principal Linux Kernel Engineer
On 14/12/17 13:44, David Miller wrote:
From: Eric Saint Etienne <eric.saint.etienne@xxxxxxxxxx>
Date: Thu, 14 Dec 2017 11:01:58 +0000
That said this sanitization task should be on top of your sparc todo
list IMHO because the existing /dev/mdesc driver doesn't filter
anything as of today, so it leaks critical/sensitive data to the OS.
It's root only.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
