Re: [PATCH][RFC] Let even non-dumpable tasks access /proc/self/fd

Quoting Petr Baudis ([email protected]):
> This kernel patch fixes the problem by letting the process access its
> own /proc/self/fd - as far as I can see, this should be reasonably safe
> since for the process, this does not reveal "anything new". Feel free to
> comment on this.

Given that

	fd=open("/etc/shadow", "r");
	setuid(1000);
	read(fd, buf, 100);

is possible before this patch, I agree - nothing new is revealed with
this patch  :)

(I've been waiting to respond because it does make me nervous, but
it seems clear that is unwarranted)

thanks,
-serge
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH][RFC] Let even non-dumpable tasks access /proc/self/fd
    • From: Petr Baudis <[email protected]>

• Prev by Date: Re: [Ext2-devel] [RFC 0/13] extents and 48bit ext3
• Next by Date: Re: [RFC] ATA host-protected area (HPA) device mapper?
• Previous by thread: [PATCH][RFC] Let even non-dumpable tasks access /proc/self/fd
• Next by thread: EDAC, unable to reserve PCI mem region
• 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]