Control: reassign -1 x2goserver Control: found -1 4.0.1.12 Control: tag -1 moreinfo
Dear Néstor,
On Mi 08 Jan 2014 18:05:00 CET, Néstor Uribe-Patarroyo wrote:
Package: x2go-server Version: 4.0.1.12-0~809~ubuntu12.04.1
When the home folder of a user contains a non-ascii character (such
as "á", or "é") I cannot initiate an x2go session. The error is:Info: Connecting to remote host 'localhost:31004'. Info: Connection to remote proxy 'localhost:31004' established. Error: The remote NX proxy closed the connection. Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Wed Jan 8 09:52:30 2014'. Session: Session terminated at 'Wed Jan 8 09:52:30 2014'.
Login with ssh works normally.
After changing the home folder of the user to one with only ascii
characters, initiating an x2go session was possible.I am using Ubuntu 12.04.3 in the server, Ubuntu 12.10 in the client.
Client version is 4.0.1.2.Both server and client installed from
thePPA ppa:x2go/stable
Thanks for filing this bug and testing X2Go.
Please note that Posix usernames are not allowed by RFC to contain
accents on characters. Posix usernames should be ASCII only.
Normally, the home directory's basename should be identical to the
username, thus also contain ASCII-only characters.
I don't think we will provide a fix for the reported bug, as your
system does not seem to comply to Posix standards.
If you think I am wrong about this, please give feedback.
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Am 09.01.2014 09:34, schrieb Mike Gabriel:
I don't think we will provide a fix for the reported bug, as your system does not seem to comply to Posix standards.
If you think I am wrong about this, please give feedback.
I agree that we shouldn't try to fix what obviously isn't broken on our side, however, we could try to check for the issue and provide a clear error message as to what is wrong.
I don't know what programming language the particular part of x2goserver is written in, but I would hope that something like this is possible in it (pseudocode):
StrippedUsername = strip_non_ascii(Username) if StrippedUsername != Username { report_error('Username does not conform to POSIX conventions.') exit }
-Stefan