[FreeNX-kNX] Protocol mismatch or no authentication data

[Peter O'Gorman]

On Mar 8, 2007, at 5:37 AM, Fabian Franz wrote:

>> On Mar 7, 2007, at 9:51 PM, Fabian Franz wrote:
>
> Ah, I think I do understand now what you mean.
>
> You mean you patched nxserver to advertise as being a 2.1.0 and  
> such the client also then sends a 2.1.0 instead of 1.5.0 and such  
> that patch is necessary, yes?
>
> So fixing it we could just do:
>
> if client_version != 1.4.0 as no one has 1.3x clients anyway ...

Haha, okay. The "harmless" change of version was less harmless than I  
thought. I was sure that I had tried unpatched freenx, but must have  
left nxloadconfig patched :(
Thank you!

I also made these other changes:

Changed all instances of:
rev | cut -d"-" -f2 | rev
to:
awk 'BEGIN {FS="-"} {i=NF-1; print $i}'

which is a more efficient way of printing the second last field in a  
record separated by "-".

Added COMMAND_PERL key to nxloadconfig and changed all instances of  
the bareword perl to $COMMAND_PERL. perl might not be available in  
PATH and/or may not be named perl.

Made some small changes in order to allow COMMAND_MD5SUM=openssl md5  
in nxloadconfig (openssl is available on more machines than md5sum, I  
think).

There is also an issue that posix find does not take a -mmin flag.  
Having it with a granularity of days sucks though. If I were you I  
might not apply that bit of the patch.

This patch has been edited, so might not apply, sorry.

Thank you,
Peter

-------------- next part --------------
A non-text attachment was scrubbed...
Name: freenx.patch
Type: application/octet-stream
Size: 6902 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20070308/db2f4277/attachment.obj>
-------------- next part --------------