[FreeNX-kNX] How / why not use the NX protocol as X replacement

[Kissake]

I've read the documentation I can readily find.  I welcome being directed to
other documentation, so please feel free to suggest RTFM while pointing at
the specific manual you are referring to.  Places I have already looked
include the NX web site, the NeatX web site, the NeatX source, including doc
directory.

The part that most greatly confuses me is the complex setup for the NX
server, including ssh keys and the like (I am referring to the behind-the
scenes portion, with the additional user account, authentication, and
internal management protocols).

I can see the utility for enabling sharing connections to other users, and
for cutting down on the configuration (in some cases) for unsophisticated
users.  But the security issues concern me.  Why another system account with
new code?  Why not (or how, if it is possible) permit NX forwarded ssh
connections similar to X forwarding?  Why cannot session attach / disconnect
(like an X version of screen?) be accomplished entirely in user-space?

I am hoping that there is something simple that I've overlooked that makes
it all make sense.  If the answer is 'there is no reason you can't do that',
then I'd like to know how, or help make progress in that direction.

Thanks in advance for any help or information.

- Kissake

Kissake... that's the point, get it? (I got it)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090814/d0a973ac/attachment.html>