[X2Go-Dev] Problem integrating x2go into Linux-system

[Mihai Moldovan]

On 06.08.2015 05:36 PM, Heinz-Ado Arnolds wrote:
> On 06.08.2015 12:56, Heinz-Ado Arnolds wrote:
>> On 06.08.2015 11:42, Stefan Baur wrote:
>>> Am 05.08.2015 um 14:27 schrieb Heinz-Ado Arnolds:
>>>> Dear Mr. Bauer,
>>>
>>>> thanks for your immediate response!
>>>
>>>> On 05.08.2015 12:30, Stefan Baur wrote: ...
>>>>> Since you're using a custom-built Linux distribution, it would
>>>>> most likely be helpful to know what it is based on - Debian,
>>>>> Ubuntu, Fedora Core, Red Hat, ... and the corresponding version
>>>>> number.
>>>
>>>> Our system is build from scratch, no package manager. I used 
>>>> x2goclient-4.0.5.0 x2goserver-4.0.1.19 nx-libs-3.5.0.32.tar.gz
>>>
>>>> System environment: gcc-5.2.0 glibc-2.21 linux-4.1.3

The reason I asked for how you built nx-libs is because I'd like to make sure
that you included all patches prior to building.

Our nx-libs source tree is pretty much what NoMachine released as their 3.5.0
version. The "good bits" are really packed up as patches, that need to be
applied before running the actual compile job.

If you used the official tarballs, the patches should already be included,
though, and no special handling required.

The nx-libs.spec file is my favorite documentation of how to build nx-libs.


>>>> Would be really great if you have a look at client-sessions1:
>>>
>>>> Proxy: Identified message of 14 bytes for FD#6 channel ID#1. 
>>>> handleWrite: Called for FD#6. handleWrite: Decoding messages for
>>>> FD#6 with 14 bytes in the buffer.
>>>
>>>> a working connection shows
>>>
>>>> Proxy: Identified message of 50 bytes for FD#6 channel ID#1. 
>>>> handleWrite: Called for FD#6. handleWrite: Decoding messages for
>>>> FD#6 with 50 bytes in the buffer.
>>>
>>>> I assume that the fake cookie can't be set. Di you have any hint
>>>> where to look for this?

It looks suspicious, I agree. Like missing data.


> I'm quite sure that my first guess is the real reason for my problem:
> The fake cookie is never saved to ~/.Xauthority.
> 
> When I look at the server side,
> 
>  XOpenDisplay()
>    X11TransConnectDisplay()
>      GetAuthorization(..., auth_namep, auth_namelenp, auth_datap,
> auth_datalenp)
> 
> I see that GetAuthorization() doesn't return any values in xauth_name
> and xauth_data (which I can even verify with a simple "xauth list").
> Debug output shows:
>  in GetAuthorizatioin() xauth_name: (null), xauth_data: (null).
>  in GetAuthorizatioin() family: 256, saddrlen: 6, saddr: ncd-11, strlen
> (dpynumbuf): 2, dpynumbuf: 50, authptr: (null).
> 
> Can anybody give me a hint where (in the code) the fake cookie is stored
> into ~/.Xauthority please?


I currently do not know where the auth cookie is saved, sorry. Will need to take
a closer look (and even then...)



Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://lists.x2go.org/pipermail/x2go-dev/attachments/20150809/d5200ab5/attachment.pgp>