summaryrefslogtreecommitdiffstats
path: root/lib/libpam/modules
Commit message (Collapse)AuthorAgeFilesLines
...
* Fixed xref.ru2005-01-212-3/+3
|
* NOCRYPT -> NO_CRYPTru2004-12-211-2/+2
|
* NOINSTALLLIB -> NO_INSTALLLIBru2004-12-211-1/+1
|
* NODOCCOMPRESS -> NO_DOCCOMPRESSru2004-12-211-2/+2
| | | | | | | | NOINFO -> NO_INFO NOINFOCOMPRESS -> NO_INFOCOMPRESS NOLINT -> NO_LINT NOPIC -> NO_PIC NOPROFILE -> NO_PROFILE
* Add knob NO_NIS (fka NO_YP_LIBC) and make world compileable when set.bz2004-11-131-3/+7
| | | | | | | | | | | If turned on no NIS support and related programs will be built. Lost parts rediscovered by: Danny Braniss <danny at cs.huji.ac.il> PR: bin/68303 No objections: des, gshapiro, nectar Reviewed by: ru Approved by: rwatson (mentor) MFC after: 2 weeks
* For variables that are only checked with defined(), don't provideru2004-10-241-3/+3
| | | | any fake value.
* Join the 21st century: Cryptography is no longer an optional componentcperciva2004-08-063-3/+0
| | | | | | | | | | of releases. The -DNOCRYPT build option still exists for anyone who really wants to build non-cryptographic binaries, but the "crypto" release distribution is now part of "base", and anyone installing from a release will get cryptographic binaries. Approved by: re (scottl), markm Discussed on: freebsd-current, in late April 2004
* Downgrade WARNS level for GCC 3.4.2.kan2004-07-281-0/+1
|
* Markup nits.ru2004-07-051-2/+2
|
* Sort SEE ALSO references (in dictionary order, ignoring case).ru2004-07-041-1/+1
|
* Mechanically kill hard sentence breaks.ru2004-07-0216-19/+23
|
* Deal with unsafe tab characters.ru2004-07-021-1/+3
|
* Markup, grammar, punctuation.ru2004-07-012-3/+3
|
* Revert the last change. There are more 64bit platforms than amd64, andkan2004-06-251-1/+1
| | | | they break due to diferent alignment restrictions.
* Remove the use of cast as lvalue.kan2004-06-251-1/+1
|
* Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror)markm2004-03-051-1/+1
| | | | | | | | | | | | | | | that this provokes. "Wherever possible" means "In the kernel OR NOT C++" (implying C). There are places where (void *) pointers are not valid, such as for function pointers, but in the special case of (void *)0, agreement settles on it being OK. Most of the fixes were NULL where an integer zero was needed; many of the fixes were NULL where ascii <nul> ('\0') was needed, and a few were just "other". Tested on: i386 sparc64
* style cleanup: Remove duplicate $FreeBSD$ tags.cperciva2004-02-101-2/+0
| | | | | | | | These files had tags after the copyright notice, inside the comment block (incorrect, removed), and outside the comment block (correct). Approved by: rwatson (mentor)
* Fix numerous constness and aliasing issues.des2004-02-106-19/+18
|
* Put libraries in the link order.ru2004-02-041-3/+2
| | | | Reported by: lorder(1) (modified to work with libraries)
* This module doesn't use libgssapi (and it looks never did).ru2004-02-041-3/+2
|
* Implement pam_sm_close_session().des2004-01-261-1/+13
| | | | | PR: bin/61657 Submitted by: Joe R. Doupnik <jrd@cc.usu.edu>
* Deal better with the crypto version of the PAM library that goesru2004-01-183-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | on the release media -- only put what is different in the crypto version compared to the base version. This reduces PAM entries in /usr/lib in the "crypto" distribution to: libpam.a libpam.so@ libpam.so.2 pam_krb5.so@ pam_krb5.so.2 pam_ksu.so@ pam_ksu.so.2 pam_ssh.so@ pam_ssh.so.2 The libpam.so* is still redundant (it is identical to the "base" version), but we can't set DISTRIBUTION differently for libpam.a and libpam.so. (The removal of libpam.so* from the crypto distribution could be addressed by the release/scripts/crypto-make.sh script, but then we'd also need to remove redundant PAM headers, and I'm not sure this is worth a hassle.)
* Remove crossref to pam.conf(5) which never existed.schweikh2004-01-171-1/+0
|
* Fix a strict aliasing issue. Also remove an unnecessary pam_get_item()des2003-12-111-8/+6
| | | | | | | call (pam_get_authtok() will return the previous token if try_first_pass or use_first_pass is specified). Incidentally fix an ugly bug where the buffer holding the prompt was freed immediately before use, instead of after.
* More strict aliasing fixes.des2003-12-111-26/+29
| | | | Submitted by: Andreas Hauser <andy-freebsd@splashground.de>
* Fix strict aliasing breakage in PAM modules (except pam_krb5, which needsdes2003-12-119-42/+44
| | | | more work than the others). This should make most modules build with -O2.
* Fix on sparc64.sobomax2003-11-121-1/+1
| | | | | Reported by: rwatson/tinderbox MFC after: 2 weeks
* Add a new configuration variable - nas_ipaddr, which if set allows tosobomax2003-11-122-8/+47
| | | | | | | | set NAS-IP-Address attribute in requests generated by the pam_radius module. This attribute is mandatory for some Radius servers out there. Reviewed by: des MFC after: 2 weeks
* - fix to UID test description, non-zero -> zerokensmith2003-10-171-1/+1
| | | | | | PR: docs/57799 Reviewed by: des Approved by: blackend (mentor)
* Ignore ECHILD from waitpid(2) (our child may have been reaped by thedes2003-09-191-1/+2
| | | | | | calling process's SIGCHLD handler) PR: bin/45669
* Revert previous commit after fixing libpam.des2003-07-211-1/+1
|
* Add a __DECONST() to unbreak the build.des2003-07-151-1/+1
|
* Fix the master yppasswd routines, so they really workmbr2003-06-151-0/+26
| | | | | | | | for root on ypmaster. yppasswd_local() did use YPPASSWDPROG instead of MASTER_YPPASSWDPROG, and the domain was not set, resulting in a coredump during xdr-encode. Reviewed by: des
* Retire pam_wheel(8) (which has been disconnected for quite a while) anddes2003-06-016-657/+0
| | | | pam_ftp(8).
* Update copyright dates.des2003-05-315-5/+5
|
* Remove all instances of pam_std_option()des2003-05-315-167/+58
|
* Introduce pam_guest(8) which will replace pam_ftp(8).des2003-05-314-1/+220
|
* mdoc(7) fixes.ru2003-05-241-4/+4
| | | | Approved by: re (blanket)
* Retire the useless NOSECURE knob.des2003-05-191-2/+1
| | | | Approved by: re (scottl)
* Turn MAKE_KERBEROS5 into NO_KERBEROS by negating the logic. Some extramarkm2003-05-051-1/+1
| | | | | cleanups were necessary in release/Makefile, and the tinderbox code was syntax checked, not run checked.
* Make sure rhostip is always initialized.des2003-04-301-1/+1
| | | | | PR: bin/51508 Submitted by: Peter Grimshaw <peter@tesseract.demon.co.uk>
* Treat an empty PAM_RHOST the same as a NULL one.des2003-04-304-5/+5
| | | | PR: bin/51508
* Set $HOME to the correct directory (within the chroot tree).des2003-04-301-0/+1
|
* Remove a bogus null password check which assumed that a user with an emptydes2003-04-241-2/+8
| | | | | | password must necessarily have an empty pwd->pw_passwd. Also add a check that prevents users from setting a blank password unless the nullok option was specified. Root is still allowed to give anyone a blank password.
* Connect the pam_chroot(8) module to the build.des2003-04-081-0/+1
|
* Add a cwd option which specifies where to chdir(2) after the chroot(2).des2003-04-082-6/+22
| | | | | When using the /home/./foo scheme, this defaults to the rhs (/foo); otherwise it defaults to /.
* Experimental pam_chroot module (not connected to the build)des2003-03-303-0/+193
|
* This module is not WARNS-clean, due to brokenness in OpenSSL headers.des2003-03-101-0/+1
|
* Somewhat better wording.des2003-03-101-8/+6
|
* Silence warning caused by OPIE brokenness.des2003-03-101-2/+3
|
OpenPOWER on IntegriCloud