libcrypt: do you mean the crypt(3) function?

I have found an EXPECT cgi program which changes the password using
information passed to it through a web form.  Unfortunately, with my
current version expect none of the password scripts (autopasswd, etc.)
work.  Someone had mentioned previously that an earlier version of
expect will solve the problem.

Does anyone know of the location of the rpm. Since expect is dependent
on the TCL/TK toolkits, do I have to change the the tcl/tk version.  I
have a RH4.2 and am hesitent to compile expect and tcl.  I would rather
stick to working rpms.


Thanks.

Eric L. Green wrote:

> On Thu, 9 Apr 1998, Trevor Astrope wrote:
> > > > On Wed, 8 Apr 1998, Bug Hunter wrote:
> > > > >     You can simply add a line in /etc/passwd, with the shell
> set to
> > > > /dev/null,
>       /bin/true or /usr/bin/passwd would be better as a shell... make
> sure to add it to /etc/shells too...
>
> > What if you don't want to allow ftp access as well? If the shell is
>
> In your /etc/ftpaccess set up a "guestgroup". Then by default set all
> your
> POP user's group to that "guestgroup" and their home directory to
> "/home/ftp". "man ftpaccess" gives a good example. Then when they try
> to
> ftp into your system, they will be placed into the same old anonymous
> ftp
> directory as "really" anonymous users.
>
> When you have a user that you want to be able to ftp to their home
> directory, just change their group to some other group. No hassles, no
>
> problems. Just be careful of umasks and permissions (should be 711 on
> the
> home directory, 755 on the public_html subdirectory, umask should be
> 022
> so that further files are created as rwxr-xr-x).
>
> Hacking on the 'adduser' script will let you do all this with little
> problem. The biggest problem is generating an initial password -- I
> get
> tired of generating and typing in initial passwords. A short Python
> script
> could solve that, but I haven't had time to mess with adduser lately.
> The
> next-to-biggest problem is letting people change their password.
> Setting
> their login shell to /usr/bin/passwd solves that to a certain extent,
> but
> some dweebs can't figure out what it means to type in "Old Unix
> Password"
> ("I typed in the new password I wanted and it won't take it!"). Sigh.
> That
> happens even if you set your /etc/issue to post complete directions on
> the
> screen -- some people just refuse to read. Oh well. Using libcrypt it
> shouldn't be very difficult to make a web front end to change
> passwords,
> but since I'm not in that business I haven't done it.
>
> Eric Lee Green   [EMAIL PROTECTED]          Executive Consultants
> Systems Specialist               Educational Administration Solutions
>  "We believe Windows 95 is a walking antitrust violation" -- Bryan
> Sparks
>
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST
> ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips
> /mailing-lists
>          To unsubscribe: mail [EMAIL PROTECTED] with
>                        "unsubscribe" as the Subject.




-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to