summaryrefslogtreecommitdiff
path: root/security/PAM
AgeCommit message (Collapse)AuthorFilesLines
2004-11-25PAM modules are dlopen'ed by the PAM library.jlam1-1/+3
2004-11-19Fix brokenness I introduced in the conversion of security/PAM to usejlam11-29/+50
libtool: the PAM libraries weren't being built with -DPAM_DYNAMIC, which made it impossible to dlopen PAM modules. Bump PKGREVISION.
2004-11-16Libtoolize security/PAM so that the appropriate options are passed tojlam16-168/+929
the compiler to build shared modules, and so that it builds correctly across different platforms. Bump the PKGREVISION. In particular, this should fix problems building this package on NetBSD/amd64.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-08-22Change the way that legacy USE_* and FOO_USE_* options are convertedjlam1-8/+3
into the bsd.options.mk framework. Instead of appending to ${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes the default options to be the union of PKG_DEFAULT_OPTIONS and any old USE_* and FOO_USE_* settings. This fixes PR pkg/26590.
2004-08-19Whitespace nit.jlam1-2/+2
2004-08-12First cut at supporting the built-in PAM on MacOS X. It's not thejlam1-1/+20
same as Linux-PAM, but it's close enough for the purposes of compiling programs.
2004-08-06Reorder conditions so that if make does short-circuit boolean evalutation,jlam1-3/+3
then we avoid hitting the disk if we don't need to.
2004-08-06Accidentally reversed meaning of test.jlam1-2/+2
2004-08-06Redo previous to say what we really want: we don't care if ${LOCALBASE}jlam1-2/+7
is "/usr", what we really want to check is if the pam_appl.h header found is within the ${LOCALBASE} hierarchy, which implies that it's a pkgsrc-controlled file, and hence not built-in.
2004-08-06In the rare case when LOCALBASE is /usr, don't let this thinkreed1-2/+2
that /usr/include/security/pam_appl.h means that PAM is builtin. (This is so a dependency can be registered correctly.)
2004-08-05Document libcrack build option.jlam1-1/+4
2004-07-30Convert to use bsd.options.mk. The relevant options variable to setjlam1-3/+17
for each package can be determined by invoking: make show-var VARNAME=PKG_OPTIONS_VAR The old options are still supported unless the variable named in PKG_OPTIONS_VAR is set within make(1) (usually via /etc/mk.conf).
2004-07-06Accept "yes" or "YES" for USE_LIBCRACK.jlam1-2/+2
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-05-11No longer used.snj1-74/+0
2004-05-11Remove support for buildlink2.snj1-7/+3
2004-03-29Match the template builtin.mk file in bsd.builtin.mk, and make the twojlam1-7/+2
packages that use builtin.mk files (graphics/xpm and pkgtools/x11-links) use the new format correctly.
2004-03-29Add a BUILDLINK_PKGBASE.<pkg> definition where it's not equal to <pkg>,jlam1-1/+2
e.g. "BUILDLINK_PKGBASE.gtk?= gtk+". This is mandated by the example buildlink[23].mk files in bsd.buildlink[23].mk.
2004-03-26Reverse the use of USE_DB185 in bdb.buildlink3.mk -- it defaults tojlam1-2/+1
"yes" and packages that can't use the DB-1.85 API should set it to "no". This makes the native DB the preferred DB if it exists.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-10Convert to use bdb.buildlink3.mk.jlam1-2/+2
2004-03-10Split out the code that deals with checking whether the software isjlam2-45/+22
built-in or not into a separate builtin.mk file. The code to deal checking for built-in software is much simpler to deal with in pkgsrc. The buildlink3.mk file for a package will be of the usual format regardless of the package, which makes it simpler for packagers to update a package. The builtin.mk file for a package must define a single yes/no variable USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether to use the built-in software or to use the pkgsrc software.
2004-02-18Reorder some lines so that BUILDLINK_USE_BUILTIN.<pkg> set in thejlam1-16/+18
environment overrides all other settings.
2004-02-12Create a new variable PREFER_NATIVE that has the opposite semanticsjlam2-6/+26
as PREFER_PKGSRC. Preferences are determined by the most specific instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If a package is specified in neither or in both variables, then PREFER_PKGSRC has precedence over PREFER_NATIVE.
2004-02-12Reorganize code so that any dependencies are checked as part of decidingjlam2-10/+14
whether the software is built-in or not. This facilitates implementing the forthcoming PKGSRC_NATIVE variable.
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam2-10/+6
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam2-10/+8
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam2-2/+18
BUILDLINK_PREFER_PKGSRC This variable determines whether or not to prefer the pkgsrc versions of software that is also present in the base system. This variable is multi-state: defined, or "yes" always prefer the pkgsrc versions not defined, or "no" only use the pkgsrc versions if needed by dependency requirements This can also take a list of packages for which to prefer the pkgsrc-installed software. The package names may be found by consulting the value added to BUILDLINK_PACKAGES in the buildlink[23].mk files for that package.
2004-01-24replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2004-01-24Support BUILDLINK_DEPENDS.<pkg> being a list of values.jlam1-2/+2
2004-01-12Update security/PAM to 0.77nb1:jlam1-3/+11
Actually make this package honor PKG_SYSCONFDIR. This package now looks for /usr/pkg/etc/pam.conf if PKG_SYSCONFBASE != "/etc".
2004-01-08Adding a MESSAGE file noting where these packages search for plugins orjlam2-1/+11
modules that may be added by other packages.
2004-01-08First cut at a common module.mk file to be included by PAM module packages.jlam1-0/+21
2004-01-08bl3ifyjlam3-10/+24
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-05Sow BUILDLINK_USE_BUILTIN.<pkg> and reap _NEED_<PKG> variables.jlam1-17/+9
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-4/+4
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+49
buildlink3 framework.
2003-10-18Use ${TOUCH} rather than touchcjep1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-05-22Some improvements from Jeremy C. Reed via PR 20892:wiz3-11/+47
- improved DESCRiption (and spelling fixed) - more MASTER_SITES - improved COMMENT - variable for enabling --with-libcrack - install limits.conf if under Linux - make sure it doesn't have an interactive configuration
2003-05-16Don't reference an include file that has not been installed yetwiz2-5/+5
and uses the correct HAVE_GETSPNAM. From Jeremy C. Reed in PR 21413.
2003-02-09fix compilation problems on systems that don't have ldconfig.dmcmahill3-2/+19
2003-01-28Instead of including bsd.pkg.install.mk directly in a package Makefile,jlam1-2/+2
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set to "YES". This enforces the requirement that bsd.pkg.install.mk be included at the end of a package Makefile. Idea suggested by Julio M. Merino Vidal <jmmv at menta.net>.
2003-01-13add LDFLAGS to ld arguments so libpam_misc can find libpam.grant2-4/+13
fixes build problem in Hubert's bulk-build.
2002-12-23Update security/PAM to 0.77. Changes from version 0.75 include:jlam29-747/+875
* Numerous bug fixes for most of the PAM modules, including several string length checks and fixes (update recommended!). * fix for legacy behavior of pam_setcred and pam_close_session in the case that pam_authenticate and pam_open_session hadn't been called * pam_unix: - don't zero out password strings during password changing function * pam_wheel: - feature: can use the module to provide wheel access to non-root accounts. * pam_limits: - added '%' domain for maxlogins limiting, now '*' and @group have the old meaning (every) and '%' the new one (all) - handle negative priority limits (which can apply to the superuser too). * pam_userdb: - require that all of typed password matches that in database * pam_access: - added the 'fieldsep=' argument, made a PAM_RHOST of "" equivalent to NULL Incidentally, cups-1.1.18 will once again do PAM authentication using pam_unix.so if built against PAM-0.77.
2002-10-09Unused.wiz1-64/+0
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam2-3/+55
buildlink2.mk files back into the main trunk. This provides sufficient buildlink2 infrastructure to start merging other packages from the buildlink2 branch that have already been converted to use the buildlink2 framework.
2002-01-29"This should just be -fPIC" from someone who knows more than I do.jlam1-2/+2
Thanks, Nick =)
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-18 03:39:32 +0000