Debian Bug report logs - #574516
ltspfs: requires user to be in the fuse group

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@hungry.com>

To: submit@bugs.debian.org

Subject: ltspfs: USB stick did not mount on server

Date: Thu, 18 Mar 2010 19:58:38 +0100

Package:  ltspfs
Version:  0.6-1
Severity: grave
User:     debian-edu@lists.debian.org
UserTags: debian-edu

When testing LTSP using Debian Edu based on Squeeze, inserting a USB
stick on the thin client do not result in anything being mounted on
the server, and no popup showed in KDE.

I expected at least the old behavour from lenny, where the stick was
mounted in /media/, but would prefer a popup in KDE as well.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ltspfs depends on:
ii  fuse-utils                    2.8.1-1.2  Filesystem in USErspace (utilities
ii  libc6                         2.10.2-6   Embedded GNU C Library: Shared lib
ii  libfuse2                      2.8.1-1.2  Filesystem in USErspace library
ii  libx11-6                      2:1.3.3-1  X11 client-side library
ii  python                        2.5.4-9    An interactive high-level object-o

ltspfs recommends no packages.

ltspfs suggests no packages.

-- no debconf information

Message #10 received at 574516@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Petter Reinholdtsen <pere@hungry.com>, 574516@bugs.debian.org

Subject: Bug#574516: ltspfs: USB stick did not mount on server

Date: Fri, 19 Mar 2010 13:16:45 -0700

tags 574516 help
thanks

On Thu, Mar 18, 2010 at 07:58:38PM +0100, Petter Reinholdtsen wrote:
> When testing LTSP using Debian Edu based on Squeeze, inserting a USB
> stick on the thin client do not result in anything being mounted on
> the server, and no popup showed in KDE.
> 
> I expected at least the old behavour from lenny, where the stick was
> mounted in /media/, 

i've been noticing that USB sticks don't mount if already inserted at login,
but sticks inserted after login do appear to work for me. the backports for the
same ltspfs packages work fine on lenny, which makes me suspect some
differences in udev or other packages... that issue eludes me.

after chatting in irc, sounds like this is not the case for you; it doesn't
work if inserted after login either.

some things to check:

* fuse module is loaded
* /dev/fuse is writeable by group fuse
* user is in fuse group

try debugging with a shell on the thin client. in lts.conf:

  SCREEN_07=ldm
  SCREEN_08=shell

* see if the devices show up in /dev/
* look at files in /var/run/ltspfs*


> but would prefer a popup in KDE as well.

this seems like a separate issue, really. you might be able to use the
ltspfs-mounter.d hooks. see /usr/share/doc/ltspfs/examples/kde-desktop-icons
for an example hook.


live well,
  vagrant

Message #17 received at 574516@bugs.debian.org (full text, mbox, reply):

From: Petter Reinholdtsen <pere@hungry.com>

To: 574516@bugs.debian.org

Subject: Re: Bug#574516: ltspfs: USB stick did not mount on server

Date: Mon, 22 Mar 2010 11:38:06 +0100

[Vagrant Cascadian]
> some things to check:
> 
> * fuse module is loaded
> * /dev/fuse is writeable by group fuse

Both ok.

> * user is in fuse group

This is not OK.  The user is not in the fuse group.  I investigated,
and the reason is that the pam_group module is not enabled.
pam-auth-update do not have support for pam_group yet.  This is bug
report in #370346.  Can ltspfs be configured to use
consolekit/policykit instead?  It would be better to get this working
out of the box without pam_group.

Aftet activating pam_group using the patch in #370346, the user was in
the fuse group after login, and the mounting happened on the server.
No KDE popup showed up, thought. :(

>> but would prefer a popup in KDE as well.
> 
> this seems like a separate issue, really. you might be able to use
> the ltspfs-mounter.d hooks. see
> /usr/share/doc/ltspfs/examples/kde-desktop-icons for an example
> hook.

A popup really should be the default in KDE.  The user experience suck
without it.

Happy hacking,
-- 
Petter Reinholdtsen

Message #22 received at 574516@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: Petter Reinholdtsen <pere@hungry.com>, 574516@bugs.debian.org

Subject: Re: Bug#574516: ltspfs: USB stick did not mount on server

Date: Mon, 22 Mar 2010 14:51:57 -0700

retitle 574516 ltspfs: requires user to be in the fuse group
severity 574516 wishlist
clone 574516 -1
retitle -1 ltspfs: issue KDE popups
user debian-edu@lists.debian.org
usertag -1 + debian-edu
thanks

On Mon, Mar 22, 2010 at 11:38:06AM +0100, Petter Reinholdtsen wrote:
> > some things to check:
> > 
> > * fuse module is loaded
> > * /dev/fuse is writeable by group fuse
> 
> Both ok.
> 
> > * user is in fuse group
> 
> This is not OK.  The user is not in the fuse group.  

ah, well, that's expected behavior. ltspfs is a fuse filesystem, and will not
work without permissions in the fuse group.


> I investigated,
> and the reason is that the pam_group module is not enabled.
> pam-auth-update do not have support for pam_group yet.  This is bug
> report in #370346.  Can ltspfs be configured to use
> consolekit/policykit instead?  It would be better to get this working
> out of the box without pam_group.

that would be nice, but would really require getting fuse filesystems to work
with policykit/consolekit in general, rather than specifically ltspfs.

 
> Aftet activating pam_group using the patch in #370346, the user was in
> the fuse group after login, and the mounting happened on the server.

good.


> No KDE popup showed up, thought. :(

splitting this into a separate issue- please follow up to the new bug number
with KDE popup issues.


> >> but would prefer a popup in KDE as well.
> > 
> > this seems like a separate issue, really. you might be able to use
> > the ltspfs-mounter.d hooks. see
> > /usr/share/doc/ltspfs/examples/kde-desktop-icons for an example
> > hook.
> 
> A popup really should be the default in KDE.  The user experience suck
> without it.

i do not knowing what a KDE popup even is. is it a filemanager thing? an
info/message system? is there a command that can be run to trigger a popup?


live well,
  vagrant

Message #33 received at 574516@bugs.debian.org (full text, mbox, reply):

From: David Adam <zanchey@ucc.gu.uwa.edu.au>

To: Debian Bug Tracking System <574516@bugs.debian.org>

Subject: ltspfs: patches required for robust operation (including non-fuse-group users)

Date: Wed, 20 Oct 2010 20:30:17 +0800

Package: ltspfs
Version: 0.5.3
Followup-For: Bug #574516


We've been trying to get LOCALDEV mounting working without adding all
our users to the fuser group. It can be accomplished with a file mode
change, editing a udev script, and a patch to lbmount.

 * chmod o+x /usr/bin/fusermount

 * add appropriate permissions flags to udev for /dev/fuse by editing
   /etc/udev/rules.d/91-permissions.rules to include 'MODE="0666",' on
   the KERNEL=="fuse" line.

 * patch src/lbmount.c as follows:

--- a/src/lbmount.c
+++ b/src/lbmount.c
@@ -259,6 +259,10 @@
                  pwent->pw_name);
         
         mkdir_safe(mediamount);
+        // use the calling user's group (so they don't have to be in the fuse group)
+        chown(mediamount, -1, pwent->pw_gid);
+        // restrictive umasks may deny group read permissions
+        chmod(mediamount, 0750);
 
         /* Now, create the media dir underneath the uid dir */
         
---

(note that this patch also makes lbmount more robust in the face of
restrictive umasks such as 077)

I'm not sure this patch should go into stock lbmount but perhaps a more
general version could be implemented.

Initially the chown() call set the owner to uidReal as well, but I wasn't sure
if this precipitated the exact race condition that mkdir_safe() was intended to
avoid. If it doesn't, perhaps a patch without the chmod() lines which uses
  chown(mediamount, uidReal, pwent->pw_gid();
would be more amenable for upstream use.

Message #38 received at 574516-done@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 574516-done@bugs.debian.org

Subject: Re: Bug#574516: ltspfs: requires user to be in the fuse group

Date: Thu, 14 Aug 2014 15:51:41 -0700

[Message part 1 (text/plain, inline)]

Version: 1.3-1

On 2010-03-22, Vagrant Cascadian wrote:
> On Mon, Mar 22, 2010 at 11:38:06AM +0100, Petter Reinholdtsen wrote:
>> > * user is in fuse group
>> 
>> This is not OK.  The user is not in the fuse group.  
>
> ah, well, that's expected behavior. ltspfs is a fuse filesystem, and will not
> work without permissions in the fuse group.

This no longer appears to be the case with recent versions of fuse.

ltspfs seems to work find for arbitrary users now.

Marking as done in 1.3-1, though technically, it's probably fixed in
some fuse version.


live well,
  vagrant

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.