x2go-dev September 2017

x2go-dev@lists.x2go.org

18 participants
122 discussions

Bug#966: Banner issue update
by Cherry, Andrew J. 01 Sep '17

01 Sep '17

I've done some additional testing, prompted by your mention of the banner being configured using the Banner option in sshd_config. It turns out we are *not* using the sshd config option -- instead, we are displaying the banner using the pam_echo module, configured with the following line in /etc/pam.d/sshd: auth optional pam_echo.so file=/etc/issue.net What I've found so far is that the same /etc/issue.net plays nice with x2go when configured via the Banner option, but causes an auth failure when configured using pam_echo.so. I'm going to do some more digging to see if I can figure out what the difference is. Oddly, if I cut/paste the output from the OpenSSH client (on Linux) up to and including the Password: prompt, and do a diff between the two, they are byte-for-byte identical. By the way, the reason we use pam_echo.so instead of the Banner option is because we actually have two banners -- /etc/issue/net for the standard security boilerplate which is always displayed, and /etc/issue.alcf which is normally empty but is populated with information during our scheduled maintenance windows when logins are disabled. However, I've confirmed that the problem still occurs even if I configure pam_echo.so to only display /etc/issue.net -Andrew

2 3

Bug#1202: kex error : no match for method mac algo client->server: server [hmac-sha2-256, hmac-sha2-512], client [hmac-sha1]
by J. M. van Bilsen 01 Sep '17

01 Sep '17

Package: x2goclient Version: 4.0.5.1-1 Complete system info : $ which x2goclient /usr/bin/x2goclient $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=18.1 DISTRIB_CODENAME=serena DISTRIB_DESCRIPTION="Linux Mint 18.1 Serena" $ dpkg --list | grep x2goclient ii x2goclient 4.0.5.1 -1 amd64 X2Go Client application (Qt4) WARNING my assumption is this problem will be on all x2goclient programs. After change of the security settings on sshd we cannot connect using x2go. Using portforwarding ssh -L 9999:localhost:22 someremotehost then letting x2goclient connect to localhost port 9999 works. Settings in sshd_config MACs hmac-sha2-256,hmac-sha2-512 When connecting we get error message : kex error : no match for method mac algo client->server: server [hmac- sha2-256,hmac-sha2-512], client [hmac-sha1] My assumption is client is configured using hmac-sha1 as default Problem does not surface using ssh or ssh port forwarding. Problem can be easy reproduced using raspberry with mathe and MACs hmac-sha2-256,hmac-sha2-512 in sshd_config Problem surface also with different ssh proxy servers having the MACs setting. As stated before normal connection on ssh or using port forwarding no problem.

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev September 2017