[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 152589] New: access permissions: media mounting options doesn't
From:       greatbunzinni () gmail ! com
Date:       2007-11-20 11:41:36
Message-ID: 20071120124135.152589.greatbunzinni () gmail ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=152589         
           Summary: access permissions: media mounting options doesn't
                    differentiate from execute flag or enter directory flag
           Product: kdesktop
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: faure kde org
        ReportedBy: greatbunzinni gmail com


Version:           3.5.8 (using KDE KDE 3.5.7)
Installed from:    Ubuntu RPMs

In Kubuntu, when a media storage device is made available (plug in a USB flash drive, \
turn on an external hard drive, pop in a CD, etc...) it appears that, if the device's \
file system doesn't support UNIX file permissions, those permissions are imposed by \
the OS. KDE has a nifty little feature that enables the user to pre-define those \
permissions. 

Unfortunately Kubuntu sets those permissions so that all files are ugo+rwx. That is a \
big problem, as it makes it possible for anyone to execute any program stored in any \
external media storage device. To make matters worse, the file permission options \
offered by KDE do not include any noexec flag nor do they allow to flag the files as \
not executable. The only option that resembles that is the "enter" flag that is \
offered through the "advanced permissions" dialog, which, if enabled, renders the \
device unusable.

It would be nice if KDE offered an option to mount media storage devices in such a \
way that it didn't made it possible to execute anything stored in those devices. \
Whether it was through a ugo-x applied only to the files or a -noexec flag, that \
option is badly needed.


[prev in list] [next in list] [prev in thread] [next in thread]