nanogui@linuxhacker.org

> -----Original Message-----
> From:	Alex Holden [SMTP:alex@linuxhacker.org]
> Sent:	Wednesday, December 13, 2000 1:15 PM
> To:	nanogui@linuxhacker.org
> Subject:	Access control
> 
> So, to sum up, I'm currently planning to implement a password based
> authentication method which can optionally use an MD5 hash algorithm to
> avoid sending the passwords as plaintext. Oh, and the authentication will
> be seperate from the TCP/IP networking support, so it should be possible
> to open up the permissions on the named socket and use the authentication
> in local mode too if you want.
> 
	[Simon Wood] 
	Personally I have no need to make nano-x network/multi user capable, though I expect
others (like your self) want these features. Is it possible to #def the code so that
this option(s) can be excluded in the build process so that I don't have to carry the
extra code around.

	I assume that clients that want to use this feature(s) will have to have some way of
being informed that they are to communicate with a foreign server. Will existing clients
HAVE to be re-written/re-compiled/neither, even if they don't uses this feature(s)???

	Simon W.