Re: [PATCH 0/7] procfs privacy

On Mon, 18 Apr 2005, Lorenzo Hernández García-Hierro wrote:

> - /proc/ioports
> - /proc/iomem
> - /proc/devices
> - /proc/cmdline
> - /proc/version
> - /proc/uptime
> - /proc/cpuinfo
> - /proc/partitions
> - /proc/stat
> - /proc/interrupts
> - /proc/slabinfo
> - /proc/diskstats
> - /proc/modules
> - /proc/schedstat

The same "this forces people to run system monitoring tasks
as root, potentially opening themselves up to security holes"
comment applies to this patch.

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

---

• Follow-Ups:
  • Re: [PATCH 0/7] procfs privacy
    • From: Lorenzo Hernández García-Hierro <[email protected]>

• References:
  • [PATCH 0/7] procfs privacy
    • From: Lorenzo Hernández García-Hierro <[email protected]>

• Prev by Date: Re: [PATCH 1/7] procfs privacy: /proc/bus/pci
• Next by Date: Re: [PATCH] TCP ipv4 source port randomization
• Previous by thread: [PATCH 0/7] procfs privacy
• Next by thread: Re: [PATCH 0/7] procfs privacy
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]