[FreeNX-kNX] NX 3.0 backend fails to run VNC proxy on Debian

[Jeremy Wilkins]

Fabian, I am having troubles getting FreeNX to play nicely with an nx-3.0 
backend on the side of VNC proxy.  It seems the nxpasswd which was in 
nx-2.1.0 was removed from nx-3.0.0 and vncpasswd in Debian doesn't allow 
piping the password by stdin like nxpasswd does.  However, I tried TightVNC 
sources and they allow piping with the -f switch as is posted on their online 
man pages.

Do you already have a patch for trunk related to this or should I make one?

What would you suggest as the best solution in order to maintain compliance?

I do not want to get shunned because I'm recreating the wheel here.  I was 
thinking I could make a source for our own nxpasswd and offer it for you to 
add to trunk, but I don't like the idea of duplicating code even though it 
isn't in Debian already, and I don't want to pull from outdated nx 2.1.0 
sources.  This puts me between a rock and a hard place (as the saying goes 
here).

Let me know what you think is best.

-- 
Jeremy Wilkins
306-382-8977