| View previous topic :: View next topic |
| Author |
Message |
Irets
Apprentice
Joined: 17 Dec 2019
Posts: 224
|
 Posted: Tue Jul 19, 2022 4:37 pm Post subject: [SOLVED] X2Go fails to connect after segfault |
 |
|
Hey,
I'm currently setting up X2Go server on my laptop and X2Go client on my desktop. Both are amd64 gentoo systems.
The program is using a SSH key generated using ssh-keygen -t rsa with an empty passphrase.
I've copied the contents of the generated id_rsa.pub to my laptop's server user's ~/.ssh/authorized_keys file.
The keys work when testing with ssh irets@192.168.1.101, as it logs me in instantly.
I had success trying out how different applications worked through the program up until I hit a segfault.
After restarting X2Go client, I am no longer able to access my laptop.
When attempting to launch /usr/bin/thunar using the client, it first prompts me for the passphrase to decrypt the key, and after that the password for my user account on the server. (this did not happen before the segfault.)
Giving it an empty passphrase and my password, it thinks for a moment before giving me a dialog box stating:
| Code: | Access denied for 'keyboard interactive'. Authentication that can continue: publickey,password,keyboard-interactive
Access denied for 'password'. Authentication that can continue: publickey,password,keyboard-interactive
Access denied for 'password'. Authentication that can continue: publickey,password,keyboard-interactive |
Here's the sshd_config file of my server:
| Code: | # $OpenBSD: sshd_config,v 1.104 2021/07/02 05:11:21 dtucker Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key
# Ciphers and keying
#RekeyLimit default none
# Logging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
#PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
#PubkeyAuthentication yes
# The default is to check both .ssh/authorized_keys and .ssh/authorized_keys2
# but this is overridden so installations will only check .ssh/authorized_keys
AuthorizedKeysFile .ssh/authorized_keys
#AuthorizedPrincipalsFile none
#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
#KbdInteractiveAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the KbdInteractiveAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via KbdInteractiveAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and KbdInteractiveAuthentication to 'no'.
UsePAM yes
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
X11DisplayOffset 10
X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
PrintLastLog no
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none
# no default banner path
#Banner none
# override default of no subsystems
Subsystem sftp /usr/lib64/misc/sftp-server
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# PermitTTY no
# ForceCommand cvs server
# Allow client to pass locale environment variables. #367017
AcceptEnv LANG LC_ALL LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_NUMERIC LC_TIME LANGUAGE LC_ADDRESS LC_IDENTIFICATION LC_MEASUREMENT LC_NAME LC_PAPER LC_TELEPHONE
# Allow client to pass COLORTERM to match TERM. #658540
AcceptEnv COLORTERM |
So far I've tried re-running x2godbadmin --createdb, re-generating my key and restarting my laptop.
Here's how I've setup the client.
https://i.imgur.com/EcZQAMZ.png
Any clues to start troubleshooting this? I'm not very familar with X2Go.
Last edited by Irets on Tue Jul 19, 2022 4:50 pm; edited 1 time in total |
|
| Back to top |
|
 |
Irets
Apprentice
Joined: 17 Dec 2019
Posts: 224
|
| Posted: Tue Jul 19, 2022 4:49 pm Post subject: |
|
|
Apparently if the "Try auto login (via SSH Agent or default SSH key)" box is ticked in the client software, the path to the key in the above textbox should *not* be present.
I've got no clue how the client got into this state after the segfault, but removing the path to the keyfile and leaving the box ticked works.
I'm stumped.
Case closed, marking as [SOLVED].. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
