No subject


Fri Jan 17 03:57:02 UTC 2014


going around and messing with config files.  If this works, it may be
expanded with a few more machines.

After doing a lot of research on the matter, it seems the "best" solution is
to use the NX key (which also allows clients to work "out of the box" -- a
big plus).  I don't see this as an issue, as the actual user is then
authenticated with system auth means that (I think) are at least as strong
as password-over-ssh logins they currently have (or in some cases, remote
xdm greeter sessions).

In my research, I also ran accross several commands to automagically
configure the NX key on the server.  They worked great on my gentoo box, but
neither the RHEL4 or FC5 (which are very similar) work.  They both seem to
put their files in a very different place, too (/etc/nxserver), and their
different naming has prevented my tinkering from making it work manually
either.

So, the short form of the question:  How do I set up FreeNX server on FC5 to
use the NX key?

It appears I'm using freeNX 0.5.

(btw: I am able to make it work if I copy /etc/nxserver/client.id.rsa to my
host.  However, that breaks NX to my other two servers, and changing this
file seems to break everything on the server.  There doesn't appear to be an
obvious private key match, and I haven't been able to discover one).

Any help is appreciated!
--Jim

------=_Part_20563_12759103.1159152411861
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all:<br><br>I have FreeNX (server) installed on (currently) 3 different machines: 1 Gentoo, 1 RHEL4, and 1 FC5.  The machines are owned by different entities.  From my desktop, I need to be able to connect (with FreeNX) to all 3 without going around and messing with config files.  If this works, it may be expanded with a few more machines.
<br><br>After doing a lot of research on the matter, it seems the "best" solution is to use the NX key (which also allows clients to work "out of the box" -- a big plus).  I don't see this as an issue, as the actual user is then authenticated with system auth means that (I think) are at least as strong as password-over-ssh logins they currently have (or in some cases, remote xdm greeter sessions).  
<br><br>In my research, I also ran accross several commands to automagically configure the NX key on the server.  They worked great on my gentoo box, but neither the RHEL4 or FC5 (which are very similar) work.  They both seem to put their files in a very different place, too (/etc/nxserver), and their different naming has prevented my tinkering from making it work manually either.
<br><br>So, the short form of the question:  How do I set up FreeNX server on FC5 to use the NX key?<br><br>It appears I'm using freeNX 0.5.<br><br>(btw: I am able to make it work if I copy /etc/nxserver/client.id.rsa to my host.  However, that breaks NX to my other two servers, and changing this file seems to break everything on the server.  There doesn't appear to be an obvious private key match, and I haven't been able to discover one).
<br><br>Any help is appreciated!<br>--Jim<br>

------=_Part_20563_12759103.1159152411861--



More information about the FreeNX-kNX mailing list