On Thu, 29 Nov 2001 14:35:44 +0000, Thomas Leonard said:
> On Sat, Nov 17, 2001 at 01:19:16PM -0500, Greg Spath wrote:
> > Hello,
> > I will soon have people sharing my main computer, and I like the
> > convenience of using ROX to mount and unmount things at will. This, of
> > course, requires entries in /etc/fstab.
> > The obvious problem, is I don't want everyone knowing my passwords to
> > the mount points on my servers and therefore wish to keep them out of
> > fstab (these are samba shares).
> > Well, if I try to mount one of these through ROX's mechanisms, it
> > simply freezes my X11 session, as the mount operation requires
> > authentication.
> Freezes the X session? That seems a bit odd - any idea what's happening?
When mounting an smb share (and anything else that requires a password
as well, I assume), you are prompted (on standard input?) for the
password. I'm assuming this is what is killing things. I haven't
given it too much thought as I came up with a better (IMHO) solution:
Can we have an equivalent user 'fstab' in ~/Choices? Then each user
could have his own mount points (in addition to any system-wide he is
allowed to use), and have his passwords defined, allowing easy
mounting/unmounting with ROX, while keeping his private authentication
info unaccessable by other users. I can do this already, of course,
but then you don't get the nifty mountpoint indicators that rox uses.
I guess a roxapp could be kludged together to do all the bells and
whistles, but native support would be a better solution.
The file in ~/Choices could just be a file that defines the full
command used to mount (ie, smbmount) for each private mount point.
Format would be:
/path/to/mount/point 'mountcommand options'
Does this make sense?
Gosh, I really wish I had the time to brush up on my C and do it for
you guys. I don't think it would be too hard to implement, but I
realize you are very busy with all the other Roxy stuff :) One of
these days I hope to have time to contribute more than just ideas and
> The problem with all these password things is that setuid programs don't
> generally like reading from stdin. Eg, smbmount will open /dev/tty and try
> to get the password from that instead.
Definitely the root of the problem.
> What happens if you do this under GNOME or KDE?
> If it works, we should try to find out what it does...
I haven't tried. I don't use either of those environments. I USE ROX!