[FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

[LROUFAIL at nc.rr.com]

I looked at the code and they have not yet implemented the new session negotiation scheme for SSH connections required by 1.4.0.

I have implemented it in moznx and the source is available at http://home.nc.rr.com/moznx/.  I wish I had time to create a patch for kNX but I don't think I can.  I would be happy to help anyone who wants to understand how it works.  There is a thread in the mailing list where the Nomachine guys were very helpful with the details.

- L

----- Original Message -----
From: Tomasz Chmielewski <mangoo at interia.pl>
Date: Friday, February 18, 2005 8:00 am
Subject: [FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

> I was wondering if it is possible to use kNX from behind a 
> firewall, 
> when only port 22 is opened, and ports > 4000 are blocked?
> 
> It is possible with NoMachine NX client (enagle SSL encryption of 
> all 
> traffic in "Advanced"), but I don't see an option for that with kNX.
> 
> 
> Tomek
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
>