Re: [patch 0/8] unprivileged mount syscall

> > >>
> > >> - users can use bind mounts without having to pre-configure them in
> > >>   /etc/fstab
> > >>
> > 
> > This is by far the biggest concern I see.  I think the security 
> > implication of allowing anyone to do bind mounts are poorly understood.
> 
> And especially so since there is no way for a filesystem module to veto
> such requests.

The filesystem can't veto initial mounts based on destination either.
I don't think it's up to the filesystem to police bind/move mounts in
any way.

Miklos
-
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/

---

• Follow-Ups:
  • Re: [patch 0/8] unprivileged mount syscall
    • From: Ian Kent <[email protected]>

• References:
  • Re: [patch 0/8] unprivileged mount syscall
    • From: Andrew Morton <[email protected]>
  • Re: [patch 0/8] unprivileged mount syscall
    • From: "H. Peter Anvin" <[email protected]>
  • Re: [patch 0/8] unprivileged mount syscall
    • From: Ian Kent <[email protected]>

• Prev by Date: Re: 2.6.21-rc5: swsusp: Not enough free memory
• Next by Date: Re: [PATCH 2/2] NET: Multiqueue network device support.
• Previous by thread: Re: [patch 0/8] unprivileged mount syscall
• Next by thread: Re: [patch 0/8] unprivileged mount syscall
• 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]