Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!munnari.oz.au!uhccux!waikato!ccc_jc
From: ccc_jc@waikato.ac.nz
Newsgroups: comp.protocols.nfs
Subject: RE: Password program needed.
Message-ID: <2561.277087af@waikato.ac.nz>
Date: 19 Dec 90 20:43:10 GMT
Organization: University of Waikato, Hamilton, New Zealand
Lines: 29


>In article <3589@jaytee.East.Sun.COM>, geoff@hinode.East.Sun.COM (Geoff Arnold @
>Sun BOS - R.H. coast near the top) says:
>>[I tried to reply to Fred, but email bounced.] What behaviour
>>DO you want to see if the authentication fails? Or are you saying
>>you want a Toolkit routine to authenticate a username/password
>>and another one to set the uid/gid?
>>
>>#Good luck.  I've been trying to do this for months.  It is possible to
>>#change your uid/gid with a simple program, but I know of no simple way
>>#to authenticate a password.  In this respect, I find the toolkit very
>>#lacking.

>I must admit that I was not too clear on my last posting.  My complaint
>on the toolkit is for its lack of ability to perform the various "NET"
>functions such as logging in, mounting drives, etc.  Granted, the toolkit
>is a major strength for PC-NFS.  I would like however, not to be tied
>down to spawning NET.EXE for any network functions.  This is a slow
>process and requires more memory than some DOS shells (ie - shell to DOS
>from an application) will let you have.

Just to add my voice to the above sentiment..We are using the same procedure,
use the toolkit to authenicate then spawn to net.exe to get the login or mount
etc.
 Very slow and tedious. Some routines to link into my own programs to
perform net name, net use are what i would put on top of my wish list

John Creek
University of Waikato