Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-10-06 Thread Dominik George
Hi Andreas, I did some tests concerning this issue. I see ~/.thinclient_drives created like you describe it. It does look strange: It is owned by root, and has 755 permissions. The logged-in use can see that. Looking at it as root, it shows a lot of question marks in ls -l and is not accessible.

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-10-05 Thread Andreas Tille
Hi Dominik, On Mon, Oct 03, 2016 at 07:29:07PM +0200, Dominik George wrote: > did you find any way to reproduce the issue? > > Did you check whether it might have something to do with pam_mount? No, just back from vacation, no chance to test for the next week. > Did any of the GNOME maintainer

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-10-03 Thread Dominik George
Hi Andreas, did you find any way to reproduce the issue? Did you check whether it might have something to do with pam_mount? Did any of the GNOME maintainers reply and maybe have some idea? Cheers, Nik signature.asc Description: PGP signature

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-22 Thread Andreas Tille
[including Debian GNOME Maintainers as maintainer of gvfs into the discussion. The issue id that when using xrdp 0.9 from Jessie backports gvfs seems to have trouble with the dir ~user/.thinclient_drives] On Thu, Jul 21, 2016 at 12:16:09AM +0200, Dominik George wrote: > On Mittwoch, 20. Juli 20

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Dominik George
Hi, >May be my immediate fix will be downgrade to xrdp 0.6 to enable >users working and try to sort out things on a different machine. You could also disable device redirection with [Channels] rdpdr=0 in /etc/xrdp/xrdp.ini. -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Dominik George
On Mittwoch, 20. Juli 2016 23:03:11 CEST Andreas Tille wrote: > Hi Dominik, > > On Wed, Jul 20, 2016 at 05:58:40PM +0200, Dominik George wrote: > > Some references: > > > > http://serverfault.com/questions/188894/denied-root-access-to-user-mounted > > -fuse-file-system > > > > In conclusion, I t

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Andreas Tille
Hi Dominik, On Wed, Jul 20, 2016 at 05:58:40PM +0200, Dominik George wrote: > Some references: > > http://serverfault.com/questions/188894/denied-root-access-to-user-mounted-fuse-file-system > > In conclusion, I think it is arguable whether xrdp should create that > directory. IMHO, the behaviou

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Andreas Tille
On Wed, Jul 20, 2016 at 04:43:24PM +0200, Dominik George wrote: > > Fuse is not used on this machine […] > > Yes, it is. xrdp uses FUSE to provide shared directories from RDP > clients. OK, I was not aware of this. > You provided the link between the directory and FUSE in your original bug > re

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Dominik George
Some references: http://serverfault.com/questions/188894/denied-root-access-to-user-mounted-fuse-file-system In conclusion, I think it is arguable whether xrdp should create that directory. IMHO, the behaviour is correct. But in any case, this is not a bug, and even less an important one, becau

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Dominik George
Hi, > Fuse is not used on this machine […] Yes, it is. xrdp uses FUSE to provide shared directories from RDP clients. You provided the link between the directory and FUSE in your original bug report. > and the directory did not exist in > users $HOME dirs until they start an xrdp session with t

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Andreas Tille
Hi Dominik, On Wed, Jul 20, 2016 at 02:28:35PM +0200, Dominik George wrote: > Control: tag -1 + moreinfo > > Hi, > > > > > In MidnightCommander it is displayer in red with a leading '?' > > dated 01.01.1990 is owned by root and has all permissions unset > > (like `chmod 000 .thinclient_drives`)

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Dominik George
Control: tag -1 + moreinfo Hi, > I have installed xrdp 0.9.0~20160601+git703fedd-3~bpo8+1 on a Jessie > machine. For all users who started an xrdp session there is a new > file named > > .thinclient_drives > > This file is not accessible at all: > > # file .thinclient_drives > .thinclient

Bug#831873: xrdp created dir ${HOME}/.thinclient_drives which has permissions 000 belongs to root

2016-07-20 Thread Andreas Tille
Package: xrdp Severity: important Hi, I have installed xrdp 0.9.0~20160601+git703fedd-3~bpo8+1 on a Jessie machine. For all users who started an xrdp session there is a new file named .thinclient_drives This file is not accessible at all: # file .thinclient_drives .thinclient_drives: stic