linux-kernel - Re: procfs: boot- and runtime configurable access mode for /proc/<pid> dirs

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

Date:	Thu, 24 Mar 2011 09:32:25 +0200
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Daniel Reichelt <debian@...htgeist.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: procfs: boot- and runtime configurable access mode for
 /proc/<pid> dirs

On Thu, Mar 24, 2011 at 05:09:44AM +0100, Daniel Reichelt wrote:
> the attached patch enhances the procfs code to allow for modification of
> /proc/<pid> dir access modes. It does so
> - by hard-wiring (.config) a boot-time default mode (555, 550 or 500)
> - which can be overriden by a boot parameter piddir_mode
> - and also introduces an inode /proc/piddirs (644) which enables
> runtime-configuration (already existing pid-dirs will be updated on next
> access)

> Let me know what you think and please CC me on replying.

Keeping u/g/o inside kernel is horrible.

What is the usecase? Content of /proc/* is identical.
--
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/