| History log of /src/usr.bin/passwd/pam_passwd.c |
| Revision | | Date | Author | Comments |
| 1.7 |
| 10-Sep-2021 |
rillig | usr.bin: remove unnecessary lint comment CONSTCOND
Since 2021-01-31, lint no longer warns about 'do ... while (0)'.
No functional change.
|
| 1.6 |
| 09-Mar-2010 |
joerg | Do not call pam_end with an invalid handle if pam_start failed.
From Richard Hansen.
|
| 1.5 |
| 02-Mar-2010 |
gdt | Log successful and unsuccessful attempts to change passwords, via -l
or pam, to ease IT audit guideline compliance. Patch from Richard
Hansen of BBN in private mail.
Proposed on tech-kern with positive comments, except a suggestion I
didn't implement:
A possible future enhancement is refraining from logging if the old
password is empty, as some people abort password changing that way.
However, it's not clear if this complies with most guidelines that
require password change logging, and at first glance that appears to
be a fairly difficult change.
|
| 1.4 |
| 06-May-2007 |
jnemeth | branches: 1.4.18; 1.4.24;
Display a message indicating who's password is being changed, as per
Jeremy Reed on tech-userlevel.
|
| 1.3 |
| 26-Feb-2005 |
thorpej | branches: 1.3.2; 1.3.4; 1.3.10; 1.3.12;
Magor rework of passwd(1) for the PAM case. Add "-d <database>" option,
similar to Solaris's "-r <repository" or Mac OS X's "-i <infosystem>",
to select the password database (files, nis, krb5). Otherwise, we default
to using whatever PAM decides.
|
| 1.2 |
| 24-Feb-2005 |
thorpej | Add missing RCS ID.
|
| 1.1 |
| 22-Feb-2005 |
christos | Add a PAM passwd module.
XXX: This avoids the issue of supporting separate -l -y -k, but is the behavior
correct? Should passwd -p disable all other passwd methods? Should it become
the default if compiled in?
|
| 1.3.12.1 |
| 08-May-2007 |
pavel | Pull up following revision(s) (requested by jnemeth in ticket #626):
usr.bin/passwd/pam_passwd.c: revision 1.4
Display a message indicating who's password is being changed, as per
Jeremy Reed on tech-userlevel.
|
| 1.3.10.1 |
| 08-May-2007 |
ghen | Pull up following revision(s) (requested by jnemeth in ticket #1776):
usr.bin/passwd/pam_passwd.c: revision 1.4
Display a message indicating who's password is being changed, as per
Jeremy Reed on tech-userlevel.
|
| 1.3.4.1 |
| 08-May-2007 |
ghen | Pull up following revision(s) (requested by jnemeth in ticket #1776):
usr.bin/passwd/pam_passwd.c: revision 1.4
Display a message indicating who's password is being changed, as per
Jeremy Reed on tech-userlevel.
|
| 1.3.2.1 |
| 08-May-2007 |
ghen | Pull up following revision(s) (requested by jnemeth in ticket #1776):
usr.bin/passwd/pam_passwd.c: revision 1.4
Display a message indicating who's password is being changed, as per
Jeremy Reed on tech-userlevel.
|
| 1.4.24.1 |
| 21-Apr-2010 |
matt | sync to netbsd-5
|
| 1.4.18.2 |
| 20-Nov-2010 |
riz | Pull up following revision(s) (requested by gdt in ticket #1360):
usr.bin/passwd/pam_passwd.c: revision 1.5
usr.bin/passwd/local_passwd.c: revision 1.34
Log successful and unsuccessful attempts to change passwords, via -l
or pam, to ease IT audit guideline compliance. Patch from Richard
Hansen of BBN in private mail.
Proposed on tech-kern with positive comments, except a suggestion I
didn't implement:
A possible future enhancement is refraining from logging if the old
password is empty, as some people abort password changing that way.
However, it's not clear if this complies with most guidelines that
require password change logging, and at first glance that appears to
be a fairly difficult change.
|
| 1.4.18.1 |
| 17-Mar-2010 |
snj | Pull up following revision(s) (requested by joerg in ticket #1333):
usr.bin/passwd/pam_passwd.c: revision 1.6
Do not call pam_end with an invalid handle if pam_start failed.
From Richard Hansen.
|
