Thanks, yes, it works with other passwords with a more ASCII-like character set. We've got a limit on frequency of password changes, so I haven't experimented a lot with what works and what doesn't. We've got quite a few people successfully using X2Go at the minute (meant to mention in the report, thanks to all the X2Go developers, it's been incredibly useful!), and this is the first time we've encountered this problem. If it's useful I could create a non-AD account temporarily to test variations if it would help.
On Thu, 22 Oct 2020 at 12:52, Ulrich Sibiller <ulrich.sibil...@gmail.com> wrote: > > Well, converting the pound sign to Latin1 works, because Latin1 has > the character, but if the other side expects utf-8, too, it should be > converted back to utf-8 first, I assume. > > In utf-8 it is 0xC2 0xA3 > in Latin1 it is 0xA3. > > Have you tried using a password without special characters (just as a test)? > > Uli > > On Thu, Oct 22, 2020 at 1:01 PM Ian Malone <ibmal...@gmail.com> wrote: > > > > Hi, > > > > After a password change I found the following being rejected by x2go, > > logs on the host machine just showed the password failing. This was an > > AD password (now changed!) and direct access with plain ssh to the > > same host and other contexts in which it was used worked, only x2go > > seemed not to handle it (so I'm confident it wasn't being entered > > wrongly): > > baggl0beBottlesp£aker > > > > I get the "Authentication failed" "Access denied for 'password'. > > Authentication that can continue: > > publickey,gssapi-keyex,gss-with-mic,password" error popup. > > > > I've found an old unresolved bug report that suggests the £ character > > may be the problem, the reporter attached a patch which suggests > > changes from QString::toAsci to QString::toUtf8 in a number of places. > > https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=926 looking at git > > some of these lines are currently using toLatin1 > > https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=src/sshmasterconnection.cpp;h=667e0efeaca947cb3173d316eb05fac1544880ee;hb=refs/heads/master#l1245 > > which I'd have thought would be okay with £, so possibly something > > else is wrong (too long?). Another from around the same time relates > > to using cyrillic characters in passwords > > https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=754 > > > > Client is x2goclient-4.1.2.2-1.fc30.x86_64 (Linux, Fedora 30) > > Host is x2goserver-common-4.1.0.3-3.el7.noarch > > x2goserver-4.1.0.3-3.el7.x86_64 (Linux, RHEL 7) > > Although I also tried an older host. > > > > /var/log/secure on the host looks like this (with names and IPs obfuscated): > > Oct 21 11:35:17 XXX sshd[6207]: pam_sss(sshd:auth): authentication > > failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=XXX user=XXX > > Oct 21 11:35:17 XXX sshd[6207]: pam_sss(sshd:auth): received for user > > XXX: 17 (Failure setting user credentials) > > Oct 21 11:35:19 XXX sshd[6207]: Failed password for XXX from x.x.x.x > > port 45216 ssh2 > > Oct 21 11:35:19 XXX sshd[6207]: Received disconnect from x.x.x.x port > > 45216:11: Bye Bye [preauth] > > Oct 21 11:35:19 XXX sshd[6207]: Disconnected from x.x.x.x port 45216 > > [preauth] > > > > > > -- > > imalone > > _______________________________________________ > > x2go-dev mailing list > > x2go-dev@lists.x2go.org > > https://lists.x2go.org/listinfo/x2go-dev -- imalone _______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
