Hi Paul,

On  Di 28 Okt 2014 00:17:55 CET, paul.szabo wrote:
Dear Mike,

I test your patch and it results in several nxproxy crashes ...
You have the new, patched nxproxy on both ends of the connection?
The encoding of the data has changed.

Cheers, Paul
Ah... Good point. No. And this would also be a very rare use case. In  
my test case, I had a new nxproxy on the client-side, but tested  
against a non-patched nxagent (which has libxcomp compiled-in).
nxagent and nxproxy are installed onto different systems from  
different sources (official distro archives, X2Go Client for Windows,  
etc.).
Only nxagent comes from packages.x2go.org, but people might upgrade  
the client-side, but not the server-side and vice versa.
So, this should be handled by your code then, I guess.

Glad we are about to narrow that down, actually.

Greets,
Mike

--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

Attachment: pgphOo9j7Jt3_.pgp
Description: Digitale PGP-Signatur

Reply via email to