[FreeNX-kNX] FreeNX-kNX Digest, Vol 40, Issue 19

[dewey hylton]

Quoting Jeremy Wilkins <wjeremy at shaw.ca>:

> Date: Sun, 16 Dec 2007 22:06:17 -0800 (PST)
> From: Jeremy Wilkins <wjeremy at shaw.ca>
> Subject: Re: [FreeNX-kNX] missing nxpasswd
> To: freenx-knx at kde.org
> Message-ID: <14370092.post at talk.nabble.com>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> This is great, I'm glad it works for you.  I have found that this script
> does
> not work on Ubuntu Gutsy.  I'm not sure about previous versions.  It seems
> the vncpasswd version in Ubuntu does not accept piped data.  Instead, it
> still forces entry by keyboard (which doesn't work for automation).  I'm
> sure this is a Debian packaging issue, so I plan on creating a vncpasswd
> package that uses modified sources of a recent version of vncpasswd from
> RealVNC.  This wouldn't be a violation in my opinion of the Debian packaging
> rules since it won't accomplish the same result.
> 
> 
> Jeffrey Borg-2 wrote:
> > 
> > Hi,
> > 
> > I was trying to connect to a vnc server via nx this morning but noticed
> > on my gentoo box the nxpasswd command in no longer there.And honce the
> > passwd file wasn't created.
> > 
> > the vncpasswd command needs the password repeated twice into it. So I
> > quickly created this wrapper around vncpasswd
> > 
> > COMMAND_VNCPASSWD=/usr/local/bin/nxpasswd
> > 
> > The contents of the wrapper are
> > #!/bin/sh
> > read passwd
> > echo "$passwd
> > $passwd" | vncpasswd $1
> > 
> > 
> > 
> > I think this will still have problems as vncpasswd has limitations. eg
> > min length 6 characters etc...
> > 
> > Regards
> > 
> > Jeffrey Borg

you could also just use expect, which may be easier than dealing with a patched
source - though it would add an additional dependency.