Jane Kramer wrote:
>
> Hi,
>
> I'm disappointed to discover how trivial the Triviality Checks under
> Enhanced Security really are, and that the Help available through the
> GUI interface is wrong (Triviality checks don't really force at least 2
> characters and at least one digit or special character in passwords).
>
> I'd like to implement Site Triviality Checks, to enforce stricter rules
> on personally chosen passwords, and make sure that nothing in the GECOS
> field can be used as a password.
>
> I'm finding very little information on how to implement Site Triviality
> Checks, or the /tcb/bin/pwpolicy file. Has anyone done this, and can
> you explain how you've done it, or give pwpolicy examples?
That was my original posting. Only one person responded, but he didn't
have direct information for me. I called the DEC hotline, and after
much searching there, they were able to provide me with a C program that
does defined customer-policy callouts; I haven't had the time to
decipher the program.
I am currently working on my own password-changing program, based
heavily on the example in O'Reilly's "Programming Perl" book, trying to
work into that the ability to reference and update the Enhanced Security
database.
Jane Kramer
--
====================================================================
Jane Kramer
Computer Systems Manager, Oberlin College
Jane.Kramer_at_oberlin.edu
440-775-6929
====================================================================
Received on Tue Jun 23 1998 - 00:29:29 NZST