x2go-user July 2016

x2go-user@lists.x2go.org

17 participants
23 discussions

Re: [X2Go-User] ssh kex error
by is＠k4ts.net 13 Nov '18

13 Nov '18

Am 19.10.2015 17:06, schrieb Robert Dinse: > the new version of openssh disabled certain insecure > ciphers... Version7 is what you mean. I use 6.9 on both client and server. > you can add > the following line to your /etc/ssh/sshd_config manually enable the > insecure old ciphers: > > KexAlgorithms > curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 Adding these ciphers doesn't help - same algo error, Thats wired coz I can ssh to the server without any issues. > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- > Eskimo North Linux Friendly Internet Access, Shell Accounts, and > Hosting. > Knowledgeable human assistance, not telephone trees or script > readers. > See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) > 246-6874. > > On Mon, 19 Oct 2015, is(a)k4ts.net wrote: > >> Date: Mon, 19 Oct 2015 15:12:43 +0200 >> From: is(a)k4ts.net >> To: x2go-user(a)lists.x2go.org >> Subject: [X2Go-User] ssh kex error >> >> hi, i'm not able to connect >> to my new hardened gentoo server using x2go. >> >> No matter which key type i select for the connection, >> the client (v. 4.0.5.0) terminates with the following: >> >> kex error : no match for method server host key algo: >> server [ssh-rsa,ssh-ed25519], client [ecdsa-sha2-nistp256] >> >> I have rsa and ed25519 keys on my client and server. >> >> sshing from the shell works like always. log is attached. >> >> do you have an idea, whats might wrong? >> >> thx, >> k4t >> >> k4tfish@e10 ~ $ ssh k4tfish@host >> OpenSSH_6.9p1-hpn14v5, OpenSSL 1.0.2d 9 Jul 2015 >> debug1: Reading configuration data /etc/ssh/ssh_config >> debug1: Connecting to host.net port 51822. >> debug1: Connection established. >> debug1: identity file /home/k4tfish/.ssh/id_rsa type 1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_rsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_dsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_dsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_ecdsa type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_ecdsa-cert type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_ed25519 type -1 >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/k4tfish/.ssh/id_ed25519-cert type -1 >> debug1: Enabling compatibility mode for protocol 2.0 >> debug1: Local version string SSH-2.0-OpenSSH_6.9p1-hpn14v5 >> debug1: Remote protocol version 2.0, remote software version >> OpenSSH_6.9p1-hpn14v5 >> debug1: match: OpenSSH_6.9p1-hpn14v5 pat OpenSSH* compat 0x04000000 >> debug1: Authenticating to host...net:51822 as 'k4tfish' >> debug1: SSH2_MSG_KEXINIT sent >> debug1: SSH2_MSG_KEXINIT received >> debug1: AUTH STATE IS 0 >> debug1: REQUESTED ENC.NAME is 'chacha20-poly1305(a)openssh.com' >> debug1: kex: server->client chacha20-poly1305(a)openssh.com <implicit> >> none >> debug1: REQUESTED ENC.NAME is 'chacha20-poly1305(a)openssh.com' >> debug1: kex: client->server chacha20-poly1305(a)openssh.com <implicit> >> none >> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY >> debug1: Server host key: ssh-ed25519 SHA256:xyz >> debug1: Host '[host.net]:51822' is known and matches the ED25519 host >> key. >> debug1: Found key in /home/k4tfish/.ssh/known_hosts:203 >> debug1: SSH2_MSG_NEWKEYS sent >> debug1: expecting SSH2_MSG_NEWKEYS >> debug1: SSH2_MSG_NEWKEYS received >> debug1: Roaming not allowed by server >> debug1: SSH2_MSG_SERVICE_REQUEST sent >> debug1: SSH2_MSG_SERVICE_ACCEPT received >> debug1: Authentications that can continue: >> publickey,password,keyboard-interactive >> debug1: Next authentication method: publickey >> debug1: Offering RSA public key: /home/k4tfish/.ssh/id_rsa >> debug1: Server accepts key: pkalg ssh-rsa blen 279 >> debug1: Authentication succeeded (publickey). >> Authenticated to host ([123.123.456.7]:51822). >> debug1: Final hpn_buffer_size = 2097152 >> debug1: HPN Disabled: 0, HPN Buffer Size: 2097152 >> debug1: channel 0: new [client-session] >> debug1: Enabled Dynamic Window Scaling >> debug1: Requesting no-more-sessions(a)openssh.com >> debug1: Entering interactive session. >> debug1: client_input_global_request: rtype hostkeys-00(a)openssh.com >> want_reply 0 >> debug1: Sending environment. >> debug1: Sending env LC_COLLATE = C >> debug1: Sending env LANG = en_US.utf8 >> >> _______________________________________________ >> x2go-user mailing list >> x2go-user(a)lists.x2go.org >> http://lists.x2go.org/listinfo/x2go-user >>

3 3

Emacs crashes on start
by Roderick Johnstone 18 Sep '17

18 Sep '17

Hi I'm connecting from a Mac (X2Go Client v. 4.0.5.1 (Qt - 4.8.7)) to Fedora 24 with a xfce session using the x2goserver-4.0.1.19-11.fc24.x86_64 packages from the fedora repos. On starting emacs, I get the error below. This issue seems to have been around for a while in similar forms, but didn't affect me under Fedora 22. Is anyone in a position to confirm this issue on Fedora 24 and suggest a work around? I tried setting various environment variables suggested on various web pages for similar issues and in the bug report noted in the error message (and checked /etc/PROBLEMS), but nothing was effective. emacs starts fine in an xfce session at the console. Thanks Roderick Johnstone X protocol error: BadRequest (invalid request code or no such operation) on protocol request 131 When compiled with GTK, Emacs cannot recover from X disconnects. This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715 For details, see etc/PROBLEMS. Fatal error 6: Aborted Backtrace: emacs[0x50ad3c] emacs[0x4f11ec] emacs[0x50ade3] emacs[0x4c0f60] emacs[0x4c58b6] emacs[0x4c593b] /lib64/libX11.so.6(_XError+0x12d)[0x2b5baa0ff57d] /lib64/libX11.so.6(+0x413e7)[0x2b5baa0fc3e7] /lib64/libX11.so.6(+0x414ad)[0x2b5baa0fc4ad] /lib64/libX11.so.6(_XReply+0x238)[0x2b5baa0fd478] /lib64/libX11.so.6(XQueryPointer+0x91)[0x2b5baa0f3351] /lib64/libgdk-3.so.0(+0x4da2a)[0x2b5ba8150a2a] /lib64/libgdk-3.so.0(+0x6a605)[0x2b5ba816d605] /lib64/libgdk-3.so.0(gdk_window_get_device_position_double+0x10b)[0x2b5ba8143d1b] /lib64/libgdk-3.so.0(gdk_window_get_device_position+0x2d)[0x2b5ba8143e1d] /lib64/libgtk-3.so.0(+0x321199)[0x2b5ba7b48199] /lib64/libgtk-3.so.0(+0x3216f4)[0x2b5ba7b486f4] /lib64/libgdk-3.so.0(+0x253d8)[0x2b5ba81283d8] /lib64/libglib-2.0.so.0(+0x4a173)[0x2b5ba97d0173] /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x163)[0x2b5ba97cf703] emacs[0x5e0b78] emacs[0x5a6025] emacs[0x4fc1bc] emacs[0x4fdfdd] emacs[0x4ffc24] emacs[0x564642] emacs[0x4f16b4] emacs[0x5645e3] emacs[0x4f1670] emacs[0x4f5e6b] emacs[0x4f61c8] emacs[0x419b52] /lib64/libc.so.6(__libc_start_main+0xf1)[0x2b5bb17db731] emacs[0x41a639] Aborted (core dumped)

8 20

Logging x2go connections?
by Grigory Shamov 04 May '17

04 May '17

Hi All, This perhaps is a trivial question: but is it possible to somehow log/check history of past x2go session on the server? -- Grigory Shamov Westgrid/ComputeCanada Site Lead University of Manitoba E2-588 EITC Building, (204) 474-9625

6 6

Shared Folders?
by KARL A. WOELFER 25 Jan '17

25 Jan '17

I am not able to get the basic Shared Folder capability to run. Debian 7 Linux OS on client and server, X2go V 4.0.3.0, and XFCE Desktop. Is there something fundamental preventing this from working? Thanks in advance, - KarlW

4 5

Num Lock key in windows agent
by Olivier BILHAUT 24 Nov '16

24 Nov '16

Hi all. First of all, I'd like to congratulate all the contributors for this great work. X2go is a professional class tool for remote desktop. However... I ran into a really special thing using the windows agent in its last version (4.0.5). Sometimes, when you open the session, the "Num Lock" is usable, sometimes not. I mean, sometimes you may push the caps lock button and switch from arrows to Numeric keys, and sometimes the Key Pad is fully unusable. It happens only on windows agent as far as I know. All that I tried did not solve the issue. Did you already encounter that? Thanks. -- OB SySAdmin Fondation Hospitalière de la Miséricorde

2 2

x2goclient session icons not working
by Will Wagner 23 Nov '16

23 Nov '16

Hello, I have upgraded to 4.0.4.0 on win32. It's a minor thing but if I now set a session icon for a connection it is not displayed and I get blank instead. Is there something I need to do to get this to work? Thanks Will

3 6

X2Go Two-factor-authentication with SecurID
by swizz ly 23 Nov '16

23 Nov '16

5 16

why can't you specify the target server using x2goclient from the CLI
by brian mullan 25 Aug '16

25 Aug '16

*pyhoca-cli* has the *--server* option to specify the IP of the target desktop server but using *x2goclient* from the CLI apparently *does not* provide that option ? is there a reason it doesn't or couldn't ? thanks Brian

2 2

x2go TCE ip of clients
by ECF Solutions 28 Jul '16

28 Jul '16

Hello again, I have a server (UBUNTU 14.04) and a TCE with several thinclients. They are connected to the server by a separate network and get their IPs from the DHCP running on the (pxe)server. I know - on the server - to get the names of the (via x2go) logged in users but I need the IP address of the thinclient as well - means e.g.: bert - 192.168.0.50 eve - 192.168.0.51 a.s.o. Is there a (simple) way to get this info? No, I can't work with static IPs for the clients and my users are not always using the same client ... Thanks for any hint. Christian

2 2

Send message to all x2go-users logged in
by ECF Solutions 27 Jul '16

27 Jul '16

Hello everybody, my scenario: in my company 6 colleagues are working in the same office building as I am and 2 are only working from their home office. We are all using the same server placed "out of sight" in an other building and are connected via x2go (TCE in the office) to the server. The server (running UBUNTU 14.04) is protected against power loss by an ups that is monitored via usb and NUT on the server. The problem is to send messages regarding critical conditions (e.g. power loss) to all - via x2go - connected users. This is necessary because the NUT NOTIFYCMD script starts a controlled shutdown sequence (putting several running virtual machines to safestate a.s.o. and finally shutting down the server) after 3 minutes running on battery. These messages are send by nut via wall automatically but this is not the way as none of the users has open a terminal - all are working under their LXDE/OpenBox GUI. I asked the internet but only found one hint - and I have to say thanks to Timotheus Pokorra <https://www.blogger.com/profile/05259914906217943114> who gave me the direction with his post: http://tpokorra.blogspot.de/2013/07/notify-all-users-logged-in-over-x2go-on… I tested this and it did not work - so I designed the following solution: (this will be a /THE part of the notifycmd script from nut) #!/bin/bash # # NUT NOTIFYCMD script PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin # ... #if [ "$NOTIFYTYPE" = "ONBATT" ] #then # compose message for wall message="$(date "+%d.%m.%Y - %H:%M:%S ")$(cat /usr/local/bin/eam01.txt)" echo $message | wall # send message to admin by e-mail echo 'EAM - '$HOSTNAME' - '$(date)' Benutzer: '$USER 'USV meldet STROMAUSFALL / ONBATT !' | mail -s 'EAM from'$HOSTNAME admin(a)xxxxx.xx # get infos for x2go-user-information benutzer=`ps xaf | grep x2goagent | grep -v grep | awk ' { print ( $(NF-2) ) }' FS='-'` # get the user names screens=`ps xaf | grep x2goagent | grep -v grep | awk ' { print ( $(NF-1) ) }' FS='-'` # get the user displays USERCOUNT="$(echo $benutzer | wc -w)" # number of users / loops # start loop / action for every logged in x2go-user START=1 i=$START while [[ $i -le $USERCOUNT ]] do user=`echo $benutzer | awk -v a=$i '{print $a}'` # transfer contents (word 1,2,3...) of $benutzer to $user display=":"`echo $screens | awk -v a=$i '{print $a}'`".0" # compose $display (word 1,2,3... from $screens)) ":" & number from $screens & ".0" # send message to each x2go-user sudo -u $user -S -H sh -c "zenity --text-info --html --display=$display --filename=/usr/local/bin/eam01.txt" </usr/local/bin/pw.txt & ((i = i + 1)) done ## Loop with one second interval to allow SIGTERM reception. #let "n = 180" #while [ $n -ne 0 ] #do # sleep 1 # let "n--" #done #echo $0: commencing shutdown | wall # upsmon -c fsd #fi I know that regarding the safety questions it is not ok to read a sudo password from a file ... we must not discuss this - but I would be glad for any better idea - btw I know the possibilities of changes in the sudoers file but don't want this at the moment. As messages I use text files because this gives me the possibility (with zenity) to use html and the users finally see this popup: If someone is interested please feel free to use and test it. I would be very much interested if someone has a better / simple solution or would be thankful for every hint regarding the improvement of the code. For the time being I tested this not within the notifycmd script - I tested the interesting parts in a separate script (simulating the notifycmd / notifytype condition) within a test environment. My life-system-test has to wait until the weekend... Best regards Christian

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user July 2016