x2go-dev December 2016

x2go-dev@lists.x2go.org

19 participants
123 discussions

Bug#1120: windows folder sharing problem
by Alex Ka 02 Dec '16

02 Dec '16

Package: x2goclient Version: 4.0.5.1-4.0.5.2 windows version - 8, 8.1, 10 The message in logs is following, and so sshd server won't start: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions 0770 for '/cygdrive/C/Users/***/.x2go/etc/ssh_host_dsa_key' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. key_load_private: bad permissions Could not load host key: /cygdrive/C/Users/***/.x2go/etc/ssh_host_dsa_key Disabling protocol version 2. Could not load host key sshd: no hostkeys available -- exiting.

1 0

Bug#1056: X2Go issue (in src:x2gobroker) has been marked as closed
by X2Go Release Manager 01 Dec '16

01 Dec '16

close #1056 thanks Hello, we are very hopeful that X2Go issue #1056 reported by you has been resolved in the new release (0.0.3.1) of the X2Go source project »src:x2gobroker«. You can view the complete changelog entry of src:x2gobroker (0.0.3.1) below, and you can use the following link to view all the code changes between this and the last release of src:x2gobroker. http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=c6cbbc1e29d858e… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2gobroker. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2gobroker Version: 0.0.3.1-0x2go1 Status: RELEASE Date: Thu, 01 Dec 2016 22:19:47 +0100 Fixes: 1056 Changes: x2gobroker (0.0.3.1-0x2go1) RELEASED; urgency=low . [ Mike Gabriel ] * debian/python-x2gobroker.preinst: + Use proper comment header explaining about preinst script argument calls (not postinst). * x2gobroker/brokers/base_brokers.py: Remove Perl code in comment that confuses the Epydoc tool. * API Documentation: Sanitize __doc__ strings to make Epydoc happy. Provide Makefile.docupload and provide html API documentation at http://code.x2go.org/doc/python-x2gobroker/ . [ Mihai Moldovan ] * New upstream version (0.0.3.1): - sbin/x2gobroker-authservice: refactor pam.pam section a bit. Always initialize opam with pam and only rewrite it with pam.pam if necessary. - x2gobroker/authmechs/pam_authmech.py: port pam.pam change to this file as well. * debian/control: - Maintainer change in package: X2Go Developers <x2go-dev(a)lists.x2go.org>. - Uploaders: add myself. Also, force a rebuild due to the changed versioning. * x2goserver.spec: - Add mandatory perl-generators Build-Requires as per https://fedoraproject.org/wiki/Changes/Build_Root_Without_Perl . [ Walid Moghrabi ] * New upstream version (0.0.3.1): - sbin/x2gobroker-authservice: adapt script to correctly use the newer python-pam module, which now exposes functionality in pam.pam with backwards compatibility. Fixes: #1056.

2 1

Bug#1117: Bug#1117: x2goclient "stuck session" for select users that cannot be resumed or terminated
by Jordan Poppenk 01 Dec '16

01 Dec '16

Dear Stephan, Thanks for your quick help and suggestions! The session listing commands you mentioned didn’t reveal the users’ sessions. But while I was investigating those ideas, I was advising my users to try using an ssh -X session in an xquartz terminal as a workaround. that produced similar errors as were being reported in x2go (X11 connection rejected because of wrong authentication). Even when attempting to log onto the server in person using their user accounts, they were booted back to the login screen. So the problem was clearly outside of x2go. I googled this new but related X11 message, and noticed it was sometimes associated with users having exceeded their disk quotas: https://www.cyberciti.biz/faq/x11-connection-rejected-because-of-wrong-auth… This was the problem! I have home folder quotas, and the users had neglected our server rules and were saving large image files to their documents folder rather than our data volume. With quota enforced on their home folders, x11 and x2go were unable to write any of the files needed for authentication. This manifests as an “authentication error” even though this is a red herring. I will now know what to check if I see this error again for specific users. I’m guessing this arises because a server can’t reveal errors during authentication for security reasons, so there's no way for a client to know whether there’s free disk space on the server until it has successfully authenticated. This likely means there's nothing an x2go client can do to know this was the problem, but perhaps it would be worth considering a helpful suggestion in this error that the problem *could* be attributable to insufficient disk space in the user’s home folder on the host machine? As for brains: it's thoughtful of you to make these suggestions, although I’m afraid I'm not a radiologist or clinician, just a brain scientist who likes to use the interface for persistent matlab desktop sessions and running numbers. We do have quite a few users, so you'd be forgiven for thinking my lab was an outfit with actual resources, but all are students and we operate on a shoestring :-) This just makes us all the more grateful for your development efforts. Cheers, Jordan Jordan Poppenk, Ph.D. Canada Research Chair in Cognitive Neuroimaging Department of Psychology and Centre for Neuroscience Studies Queen's University http://popmem.com 613-533-6009

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev December 2016