Re: klik, loop mounts, and insecurity [was: statement from one of the klik project members]

2006-01-20 Thread Matthew Palmer
On Fri, Jan 20, 2006 at 03:59:23PM +, Kurt Pfeifle wrote: Wouter Verhelst wrote on debian-devel@lists.debian.org: [Re-adding Cc to Kurt, as he's mentioned he isn't subscribed] On Fri, Jan 20, 2006 at 01:20:26PM +0800, Cameron Patrick wrote: Kurt Pfeifle wrote: The klik client

Re: klik, loop mounts, and insecurity [was: statement from one of the klik project members]

2006-01-20 Thread Sam Morris
Matthew Palmer wrote: The klik client installation needs root privileges once, to add 7 lines like this one to /etc/fstab: /tmp/app/1/image /tmp/app/1 cramfs,iso9660 user,noauto,ro,loop,exec 0 0 Doesn't this introduce a local root exploit? A user can easily write their own /tmp/app/1/image

Re: Re: klik, loop mounts, and insecurity [was: statement from one of the klik project members]

2006-01-20 Thread Kurt Pfeifle
Please try man mount. If your manpage is similar to mine, it will contain something like: snip -- OPTIONS user Allow an ordinary user to mount the file system. The name of the mounting user is written to

Re: klik, loop mounts, and insecurity [was: statement from one of the klik project members]

2006-01-20 Thread Joey Hess
Sam Morris wrote: If suidperl does not ensure that the scripts it interprets have the suid bit set, then shouldn't a critical bug be filed? The nosuid mount option does not cause the suid bit to be unset, it causes the kernel to not honor it when executing binaries. This doesn't work for

Re: klik, loop mounts, and insecurity [was: statement from one of the klik project members]

2006-01-20 Thread Don Armstrong
On Fri, 20 Jan 2006, Sam Morris wrote: AFAIK Linux only supports eight loopback mounts at a time. This won't be a problem once FUSE becomes more widespread. The default is 8; by seting the max_loop kernel option, you can increase this to 256. Don Armstrong -- You have many years to live--do