Re: Client/Server & UNIX

Wayne, When I came across this problem I had the Visual Basic Front End call a stored procedure that in turn fired up a c program that called getpwnam() and a64l() to work out if the user's password had time expired, returning non-zero if it had. And then to change it I had a VB screen send old and new passwords to a stored procedure that called a setuid c program that did all the checks that the passwd command does and crypt the password string and edit the appropriate line in /etc/passwd. Not a very elegant solution, but it works. If there is a better way I would love to hear about it. Regards, Pete. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~ Pete Harris Financial Market Software Consultants~ ~ phr@fmsc.com.au 109 Pitt St Sydney NSW 2000 ~ ~ Australia ~ ~ ~ ~ Disclaimers Apply ~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Wed, 2 Aug 1995, it was written: > I have to authorize users to access an Informix database who > will never log in to UNIX. They still must be maintained in > the UNIX password file and they cannot change their own password > because they do not have telnet or RSH or anything like them. > > What are others doing who have this problem. Am I missing something > in the Informix documentation. Is there some other way to have a > database with some access control that does not involve logging to > UNIX to maintain (especially when users expect to be able to > change their passwords periodically and management expects to > be able to force them to do so) access control. > > Thanks for any help anyone can give in this area. >