x2go-dev

x2go-dev@lists.x2go.org

1 participants
5403 discussions

Bug#868: "connection failed" "pscp" error with folder sharing
by Michael DePaulo 10 May '15

10 May '15

Package: x2goclient Version: 4.0.3.2 Tags: build-win32 When the following conditions are met: 1. You are using X2Go Client for Windows 2. You are using Kerberos 5 (GSSAPI) authentication 3. Your server-side home directory is at a path other than /home/$USER Upon connecting to an X2Go server, whether you have any folders shared or not, you receive an error like: Connection failed pscp: unable to open /home/mike/.x2go/ssh/key.dK7060: no such file or directory ("Connection failed" is bolded) Furthermore, shared folders are not actually shared. If you attempt to share a folder after connecting, you receive the same error message. This bug appears to be a limitation of when Kerberos (GSSAPI) authentication was originally introduced in x2goclient 4.0.1.2. It was introduced in commit a77d761d on 2013-12-10. I will push a commit that fixes this bug. However, it overrides all paths like "~user" with "~". In other words, it assumes that SshProcess::start_cp() will never be used to upload a file to another user's home dir, unless that other user's home dir is specified absolute. As a side note, this bug is present under the default configuration of SAMBA's winbind, which does support kerberos authentication. By default, smb.conf has set: template homedir = /home/%D/%U Where %D is the domain name, and %U is the username.

1 0

Bug#789: I fixed this: more info
by Michael DePaulo 10 May '15

10 May '15

This will be fixed in the 1st release of X2Go Client for Windows 4.0.4.0-x. The bug appeared to be caused by the fact that for at least 1 of the SSH Processes, procUuid/uuidStr is null. Thus HKEY_CURRENT_USER\\Software\\SimonTatham\\PuTTY\\Sessions would be deleted (recursively) instead of only the uuidStr subkey being deleted. I fixed it by simply adding a check to SshProcess::rmPuttyReg(). It now does nothing if uuidStr is empty or null. This is the safest solution IMHO. -Mike

1 0

Bug#625: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike DePaulo 10 May '15

10 May '15

tag #625 pending fixed #625 4.0.4.0 thanks Hello, X2Go issue #625 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=db26121 The issue will most likely be fixed in src:x2goclient (4.0.4.0). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit db261211d573cd99ed359bca6fc3219fadb70c97 Author: Mike DePaulo <mikedep333(a)gmail.com> Date: Sun May 10 11:02:42 2015 -0400 Windows: Do not delete saved PuTTY sessions when Kerberos 5 (GSSAPI) authentication is enabled (Fixes: #625) diff --git a/debian/changelog b/debian/changelog index 6536b5c..f5238a3 100644 --- a/debian/changelog +++ b/debian/changelog @@ -2,6 +2,8 @@ x2goclient (4.0.4.0-0x2go1) UNRELEASED; urgency=low [ Mike DePaulo ] * New upstream release (4.0.4.0): + - Windows: Do not delete saved PuTTY sessions when Kerberos 5 + (GSSAPI) authentication is enabled (Fixes: #625) - Windows: Include debug build in the regular installer. It is an optional component during the install. It is not installed by default.

2 1

Bug#867: LANGUAGE connection
by GERARD.CALAS＠FREE.FR 09 May '15

09 May '15

PACKAGE: x2goclient VERSION: 4.0.1.3 Hello, I live in France, I am user LINUX / Mageia / KUBUNTU / FEDORA. The X2goclient product works properly and satisfies me completely. A light BUG on internationalization is annoying. The x2goclient client (LINUX or WINDOW) is the x2goserver server in English, so that all KDE menus, level one, are in English. I have not found, or the language setting to the KDE connection. Thank you to propose a change to prende into account the language of the user. Thank you and congratulations Gerard CALAS gerard.calas(a)free.fr -- =========================================================================================== =========================================================================================== Gérard CALAS Mobile: 06 40 59 57 15 Mail: GERARD.CALAS(a)FREE.FR =========================================================================================== Ce n'est pas obligatoire de regarder les différents albums, les amateurs de la nature et du VTT y trouveront intéret, amitiés. PICASAWEB/GOOGLE ont augmenté les possibilités de stockage de 1GO à 5/15GO, merci à eux !!! Ce qui m'a permis de réorganiser les albums photos ... http://picasaweb.google.fr/gerard.calas.5 LE SOIXANTENAIRE http://picasaweb.google.fr/gerard.calas.11 VTT 2011 2012 2013 2014 http://picasaweb.google.fr/GERARD.VTT.RAID QUELQUES RAIDS VTT (2002-2008) http://picasaweb.google.fr/GERARD.VTT.BALADE QUELQUES BALADES VTT (2000-2007) http://picasaweb.google.fr/glinux13122 BALADES VTT 2008 2009 http://picasaweb.google.fr/gerard.calas.6 BALADES VTT 2010 http://picasaweb.google.fr/GERARD.SKIS SKIS JUSQU'EN 2011 http://picasaweb.google.fr/sitefamilial2 SITE FAMILIAL http://picasaweb.google.fr/GERARD.PASSAGE.1 EVENNEMENTS DIVERS =========================================================================================== Bureautique LINUX LIBREOFFICE Sur mon PC, j'utilise la version gratuite de LINUX MAGEIA 32/64 pour utilisateurs privés. LINUX est un OS sérieusement sécurisé. LINUX est insensible aux VIRUS. L'outil de messagerie THUNDERBIRD bloque de lui même les indésirables (SPAMs, SPYs etc...). Les utilisateurs des "autres mondes fenêtrés" continuent d'utiliser des produits capables de nuirent à leur propre disque dur !!! Essayez donc LINUX ( quelque soit la distribution ), pour être à l'abri des nuisances habituelles, et de plus, c'est gratuit!!! UBUNTU, MANDRIVA, FEDORA, SUSE, DEBIAN, etc... =========================================================================================== ===========================================================================================

1 0

Re: [X2Go-Dev] improve Xinerama
by Mike Gabriel 08 May '15

08 May '15

Hi Ulrich, (Re-Cc:ing x2go-dev) On Di 05 Mai 2015 23:51:16 CEST, Ulrich Sibiller wrote: > On Tue, May 5, 2015 at 12:04 PM, Mike Gabriel > <mike.gabriel(a)das-netzwerkteam.de> wrote: >> please cherry-pick this commit [1] onto your branch. It removes the >> libNX_Xinerama part from NX > > OK, done, also issued PR. I tested nxagent now. I tested two things (see below). For both tests I modified /usr/bin/x2gostartagent, so that NX_XINERAMA_CONF gets explicitly set to auto. I also removed all LD_LIBRARY_PATH related stuff from /usr/bin/x2goruncommand. 1. I built NX agent from https://github.com/sunweaver/nx-libs/tree/pr/libxinerama-cleanup (top commit hash cd8e2d5295e43098c8afbdab5591d9e46eb7c751 [1]). This build does _not_ contain your patches. -> expectexd results: (a) rootless applications in nxagent don't recognize the client-side monitor (Xinerama) layout (b) desktop sessions in nxagent don't recognize the client-side monitor (Xinerama) layout -> observed results: (a) rootless session were already Xinerama aware... (????) (b) desktop sessions in nxagent don't recognize client-side monitor (Xinerama) layout 2. I built NX agent from https://github.com/sunweaver/nx-libs/commits/feature/new-xinerama-3.6.x (top commit hash 15cccc136b6b9740ba558e02da918ad843795995). This build does contain your patches. -> observed results (a) rootless sessions are Xinerama (b.1) desktop sessions had no clue about monitor borders (no Xinerama layout) -> this was an nxagent built and launched on my notebook (amd64 system, Debian jessie) (b.2) desktop session knew about Xinerama and the desktop splitting worked fine on resize events (changing the X2Go session window size) -> moving the X2Go desktop session window across the client-side desktop should triggering a Xinerama resizing (or rather the end of movement) -> this was observed on my PC at work (i386 system, Debian jessie) I have no clue why my notebook failed to provide Xinerama inside NX agent, but maybe this should be investigated, once if have tackled the issues you addressed below. [1] https://github.com/sunweaver/nx-libs/commit/cd8e2d5295e43098c8afbdab5591d9e… [2] https://github.com/sunweaver/nx-libs/commit/15cccc136b6b9740ba558e02da918ad… >> I will have my dual head workstation around tomorrow and then test your >> code. >> >> You may meanwhile (if time allows) also test your code with [1] applied on >> top. > > Seems to work (you might need to change the code a litte to force > usage of the _auto parts when testing with x2goclient). > > However, I am not sure that this implementation represents final > solution. As you might have noticed my changes are included in the > RandrRextension code. At first I did this simply because that is the > code path that is used when Xinerama requests are issued. Meanwhile I > found this (in > http://www.x.org/archive/X11R7.7/doc/randrproto/randrproto.txt) > > ----- > 11.2 Xinerama > > Xinerama provides a mechanism for describing the relationship between the > overall screen display and monitors placed within that area. As such, it > provides the query functionality of RandR 1.2 without any of the > configuration functionality. Applications using Xinerama to discover > monitor geometry can continue to do so, with the caveat that they will not be > informed of changes when they occur. However, Xinerama configuration data > will be updated, so applications selecting for RandR notification and > re-querying the configuration with the Xinerama extension will get updated > information. It is probably better to view RandR as a superset of Xinerama > at this point and use it in preference to Xinerama where both are present. > ----- > > So basically the way to go is to let nxagent setup RandR in a way that > the RandR extension itself will work without nx specific changes. I > have been playing around with that approach yesterday and could it get > to work (kind of, with lots of problems). I will have a look at this > again soon. > > If I succeed in this approach (which I am not sure about) this would mean: > - my current code would be obsolete > - Xinerama extension could be dropped completely > - RandR extension could stay unchanged (well, except for the existing > changes introduced by nx) from the X11 distribution > - all relevant code is to be found in the nxagent directory. > > The description above also contains a hint how to avoid having to > issue an X request to the real X server whenever some inside client > issues Xinerama requests: Use RandR for that and register nxagent to > be notified of Xinerama/RandR changes. This way another roundtrip > would be eliminated. > > Does that sound reasonable? Well, the more I think things through, every NX'ish speciality in the current NX code tree has to be moved into Xserver/hw/nxagent for two reasons: o propose as few NX-specific patches as possible to X.Org upstream o every code snippet from NoMachine is licensed as GPLv2 and has to be removed from the xorg-server and lib<Xlib+extension> libraries. Thus, same for your Xinerama patches, I guess. And if it is possible to register an event that informs about Xinerama changes, the better. And if it saves us some more roundtrips, again even better. So, basically, also because of the issue about having to propose this or that patch to X.Org upstream: the more of your code that you can move into the hw/nxagent dir, the better!!! Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

2 2

Re: [X2Go-Dev] improve Xinerama
by Ulrich Sibiller 05 May '15

05 May '15

Am 29.04.2015 00:37 schrieb "Mike Gabriel" <mike.gabriel(a)das-netzwerkteam.de>: > > Hi Uli, > > (any reason for going off-list?) > Stupid Gmail client in Android... >> Well, I haven't thought about moving that code yet, but this would be a >> step in the right direction. It would solve all of the problems I mentioned >> in my first mail. But I still think the real solution would be to redirect >> xinerama requests to the real X server. Generally libnxcomp can handle all >> kinds of X11 requests so that redirection should not be too complicated. >> Caching/optimization can be implemented at a later time. > > Ok. I missed that. (Had a full day with customer tasks etc. and could only fly over mails today). >>> If you are available for coding, maybe you feel like working on the >> >> Xinerama change? >> >> I am currently looking into this. > > So cool!!! I have a working version right now that asks the real X server for xinerama data. I have to do some code cleanup and will then put that to github. However, I am still unsure about the correct solution here. Some questions that arise: - do we need a switch to disable that lookup? Why is xinerama disabled by default when configuring new x2go sessions? - do we need a notification from the nxproxy when the xinerama setup changes during connection? - xinerama is integrated into xrandr (in programs/Xserver/randr/rrxinerama.c; the file I mentioned yesterday is compiled and included, but not used apparently). Does hooking in there produce any side effects? Currently clients asking nxagent for xinerama info get the values from the real server but there are internal structures that are not updated. - is there a need to keep the current solution with LD_LIBRARY_PATH ? (I'd say no) Uli

4 12

Bug#845: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mihai Moldovan 04 May '15

04 May '15

tag #845 pending fixed #845 4.0.4.0 thanks Hello, X2Go issue #845 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=fc224ac The issue will most likely be fixed in src:x2goclient (4.0.4.0). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit fc224acfffe7ea4393410e92a692caf09cf4c94c Author: Mihai Moldovan <ionic(a)ionic.de> Date: Mon May 4 19:12:35 2015 +0200 onmainwindow.cpp: correctly let Qt fetch the UI display language for Qt 4.8.0 and higher. The old "compat" behavior is retained for older versions of Qt, which do not have the semantics of a UI display language. Fixes: #845. diff --git a/debian/changelog b/debian/changelog index 13a9e63..3832c60 100644 --- a/debian/changelog +++ b/debian/changelog @@ -349,6 +349,10 @@ x2goclient (4.0.4.0-0x2go1) UNRELEASED; urgency=low - {configdialog.{cpp,h},onmainwindow.cpp}: miscellaneous typo fixes - no functional changes. - onmainwindow.cpp: whitespace changes to installTranslator() only. + - onmainwindow.cpp: correctly let Qt fetch the UI display language for Qt + 4.8.0 and higher. The old "compat" behavior is retained for older + versions of Qt, which do not have the semantics of a UI display + language. Fixes: #845. [ Fernando Pedemonte ] * New upstream release (4.0.4.0):

2 1

Processed: Re: Bug#845: Intentional forced language?
by owner＠bugs.x2go.org 04 May '15

04 May '15

Processing control commands: > reopen -1 = Bug #845 {Done: Stefan Baur <X2Go-ML-1(a)baur-itcs.de>} [x2goclient] Windows client missing language changing option Bug reopened Ignoring request to alter fixed versions of bug #845 to the same values previously set > tags -1 - not-a-bug wontfix Bug #845 [x2goclient] Windows client missing language changing option Removed tag(s) not-a-bug and wontfix. -- 845: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=845 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Fwd: libssh 0.6.5 has been released to address CVE-2015-3146
by Michael DePaulo 04 May '15

04 May '15

Sent from my Android Smartphone ---------- Forwarded message ---------- From: "Andreas Schneider" <asn(a)cryptomilk.org> Date: Apr 30, 2015 10:33 AM Subject: libssh 0.6.5 has been released to address CVE-2015-3146 To: <libssh(a)libssh.org> Cc: ibssh versions 0.5.1 and above have a logical error in the handling of a SSH_MSG_NEWKEYS and SSH_MSG_KEXDH_REPLY package. A detected error did not set the session into the error state correctly and further processed the packet which leads to a null pointer dereference. This is the packet after the initial key exchange and doesn’t require authentication. This could be used for a Denial of Service (DoS) attack. The bug was found and reported by Mariusz Ziulek from the Open Web Application Security Project (OWASP). https://www.libssh.org/2015/04/30/libssh-0-6-5-security-and-bugfix-release/ -- Andreas Schneider GPG-ID: CC014E3D www.cryptomilk.org asn(a)cryptomilk.org

1 1

Bug#862: Please update createrepo to the latest version in Debian unstable.
by Mihai Moldovan 04 May '15

04 May '15

Package: packages.x2go.org The current version of createrepo leaves trash behind in /tmp/ every time it is executed. The most recent version in Debian unstable should fix this problem and be trivially installable due to it only being python scripts.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev