From unknown Sun Apr 26 10:56:21 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#200: [X2Go-Dev] Bug#200: Bug#200: When user-directories do not exist, saving sqlpass with x2godbadmin is not possible Reply-To: Stefan Baur , 200@bugs.x2go.org Resent-From: Stefan Baur Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Tue, 07 May 2013 21:03:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 200 X-X2Go-PR-Package: x2goserver X-X2Go-PR-Keywords: Received: via spool by 200-submit@bugs.x2go.org id=B200.13679600351259 (code B ref 200); Tue, 07 May 2013 21:03:02 +0000 Received: (at 200) by bugs.x2go.org; 7 May 2013 20:53:55 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_SORBS_WEB,SPF_HELO_PASS autolearn=no version=3.3.2 X-Greylist: delayed 451 seconds by postgrey-1.34 at ymir; Tue, 07 May 2013 22:53:55 CEST Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by ymir (Postfix) with ESMTP id 0462C5DB18 for <200@bugs.x2go.org>; Tue, 7 May 2013 22:53:54 +0200 (CEST) Received: from [192.168.0.3] (dslb-188-099-201-236.pools.arcor-ip.net [188.99.201.236]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0MSpj3-1V0vvI0rMz-00RZ5L; Tue, 07 May 2013 22:41:21 +0200 Message-ID: <518966E5.40800@stefanbaur.de> Date: Tue, 07 May 2013 22:41:09 +0200 From: Stefan Baur User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: x2go-dev@lists.berlios.de CC: "200@bugs.x2go.org" <200@bugs.x2go.org> References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:GuQCXunDmqzMvYdfIlytPrlAEgjJAgHctu7WTVatr8v ec8mDsaVtTTtUYWa8IfVnPLf5D9j8C98gyVAZYSV+TaXMRv9H+ DN0BK2NqHUhgbwr+YdHbQHGP13amPe1Cnm6oE0gGgSUJc0vx7m 0UscAdv+3ozHwxLZclEcoEtvo9O/DvBjcQDssjo9eEL8wZQO6d TB4J8LGjDxipHj9ZhlOHjOdIu2B7QQvvgbZYALp61sRILfw/Bn RbEot79pF/HljYeNQsVC7cZElPPTSsO4ICnybA9mjO/ehCo4WC KDdWFO8+c7yXLZGCL38IcHpvWlpvjQbzbjSN8UqxyLVwSHkyVi nnY858P6btZYPRNLvK5metMJ+E28eDfsbaxlhs4Fr Am 07.05.2013 22:14, schrieb Michael Kromer: > Well, I don't mind fixing this to be safe with special chars ...;) > I however really doubt administrators to set homedirs to something with spaces or special chars. I could imagine that it may well happen in a mixed Windows/Linux-Environment, where user management is done in an ActiveDirectory, and certain PAM modules are used for authentication and automatic creation of homedirs. Pimplefaced Joe Random Winadmin might use "Firstname Lastname" as account naming scheme on the Windows side. If you have a PAM mechanism in place that creates missing homedirs and simply use /home/usernamepassedfromwindows, you may end up with spaces in that directory name. Or, in a multi-domain environment, with subdirectories like /home/domain1/sampleuser and /home/domain2/johndoe. And it *might* even be possible to use a special char as a domain separator instead of creating subdirectories, like /home/domain1+johndoeindomain1 /home/domain2+johndoeindomain2. I've never tried that with PAM and autocreating home directories, but I remember that "back in the days" there were issues when connecting to multiple AD domains and thus it was recommended to use a special char as separator between AD domain and user name, rather than the standard one. Just a few words of warning from an old geezer. ;-)