summaryrefslogtreecommitdiff
path: root/security/cyrus-sasl
AgeCommit message (Collapse)AuthorFilesLines
2005-02-24Add RMD160 digests.agc1-1/+2
2005-01-14Create a pam.buildlink3.mk file that is used by PAM-using packages.jlam2-5/+5
It includes the correct buildlink3.mk file from either Linux-PAM (security/PAM) or OpenPAM (security/openpam) and eventually will support solaris-pam. pam.buildlink3.mk will: * set PAMBASE to the base directory of the PAM files; * set PAM_TYPE to the PAM implementation used. There are two variables that can be used to tweak the selection of the PAM implementation: PAM_DEFAULT is a user-settable variable whose value is the default PAM implementation to use. PAM_ACCEPTED is a package-settable list of PAM implementations that may be used by the package. Modify most packages that include PAM/buildlink3.mk to include pam.buildlink3.mk instead.
2004-12-28The default location of the pkgsrc-installed rc.d scripts is nowreed1-2/+2
under share/examples/rc.d. The variable name already was named RCD_SCRIPTS_EXAMPLEDIR. This is from ideas from Greg Woods and others. Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism (as requested by wiz).
2004-11-25These packages install libraries that dlopen() shared modules.jlam1-1/+4
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv2-4/+4
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-09-22Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.jlam1-25/+1
All library names listed by *.la files no longer need to be listed in the PLIST, e.g., instead of: lib/libfoo.a lib/libfoo.la lib/libfoo.so lib/libfoo.so.0 lib/libfoo.so.0.1 one simply needs: lib/libfoo.la and bsd.pkg.mk will automatically ensure that the additional library names are listed in the installed package +CONTENTS file. Also make LIBTOOLIZE_PLIST default to "yes".
2004-08-22Change the way that legacy USE_* and FOO_USE_* options are convertedjlam1-14/+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-07-30Convert to use bsd.options.mk. The relevant options variable to setjlam5-45/+64
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-05-09Unused.wiz1-27/+0
2004-04-23mk/bsd.pkg.install.mk now automatically registersreed1-3/+1
the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
2004-03-26PKGREVISION bump after openssl-security-fix-update to 0.9.6m.wiz3-4/+6
Buildlink files: RECOMMENDED version changed to current version.
2004-03-23bl3ify and convert to use krb5.buildlink3.mk for proper Kerberosjlam3-10/+35
detection and linkage. This fixes PR 24498.
2004-01-24replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.grant1-2/+2
2003-11-12PKGREVISION++ after openssl update.jschauma1-2/+2
2003-08-30Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL ifjlam1-1/+4
USE_PKGINSTALL is "YES". bsd.pkg.install.mk will no longer automatically pick up a INSTALL/DEINSTALL script in the package directory and assume that you want it for the corresponding *_EXTRA_TMPL variable.
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2003-03-22Correct DEPENDS line to proper formatjmc1-2/+2
2003-03-19Add a section to deal with SASL plugins, and clarify where this filejlam1-3/+8
should be included in package Makefiles.
2003-03-19Rearrange some of the Makefile logic so that we can create Cyrus SASLjlam2-63/+79
plugin packages.
2003-01-28Instead of including bsd.pkg.install.mk directly in a package Makefile,jlam1-3/+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>.
2002-12-16On NetBSD use /dev/urandom insted of /dev/random (PR#19275).martti4-8/+30
Bump PKGREVISION.
2002-10-21Fix sasl-config script so that "sasl-config --libs" returns the full listjlam5-15/+15
of libraries and linker flags needed to link against libsasl. Bump PKGREVISION and bump the BUILDLINK_DEPENDS as packages will be needing to use a version of cyrus-sasl with a correct sasl-config.
2002-10-09Unused.wiz1-54/+0
2002-10-07Use int32_t while dealing with sasldb version not long! This fix cyrus saslseb5-7/+150
on sparc64. Bump PKGREVISION.
2002-09-20Make these scripts more portable by taking advantage of automatic rc.dgrant2-4/+4
script handling and using @RCD_SCRIPTS_SHELL@. as discussed with jlam.
2002-09-19Take advantage of the auto-generation and installation of rc.d scripts.jlam1-11/+1
2002-09-18When using bsd.pkg.install.mk, if a DEINSTALL or INSTALL file alreadyjlam1-4/+1
exists, then use it as the default value of DEINSTALL_EXTRA_TMPL or INSTALL_EXTRA_TMPL.
2002-09-07Remove dependency on autoconf/automake and finish buildlink2 conversion.jlam7-25/+306
2002-08-25Merge changes in packages from the buildlink2 branch that havejlam9-13/+40
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-07-31Build and install "saslauthd", a daemon running as root that performsjlam8-18/+115
plaintext password authentication for Cyrus SASL. This will allow daemons _not_ running as root to perform SASL PLAIN authentication (including getpwent and PAM). Bump PKGREVISION to 1.
2002-07-22Use correct homepage.jlam1-2/+2
2002-03-24Make it compile with SASL_USE_GSSAPI=YES. Closes pkg/16040 bywiz3-6/+20
Rodolphe de SAINT LEGER.
2002-03-07If USE_PAM is defined, then libsasl.so is linked against libpam.so, sojlam1-1/+5
include PAM/buildlink.mk to pull it into ${BUILDLINK_DIR}.
2002-02-05Solaris' test binary (test/[) doesn't grok "-e". Replace with "-f".jlam1-3/+3
Noted by Stoned Elipot <seb@netbsd.org> in private email.
2002-01-31Remove the dbinit command as it's not needed by the pwcheck daemon.jlam1-36/+1
pwcheck only checks against the /etc/passwd database. Users that need CRAM-MD5 or SCRAM-MD5 authentication can initialize the sasldb and add themselves in the process by running saslpasswd.
2002-01-31* Create the link /usr/lib/sasl -> ${PREFIX}/lib/sasl as it's where SASL-jlam4-8/+22
aware applications look for authentication mechanisms by default. * Warn package admin if ${PREFIX}/lib/sasl is non-empty after deinstallation, as it may contain service config files. * Purge use of PKGDIR.
2002-01-31Make "dbinit" work even if not installed in /etc/rc.d.jlam1-2/+4
2002-01-31Add USE_PAM to the BUILD_DEFS if it is defined.jlam1-2/+3
2002-01-13Update to 1.5.27. Changes are mostly bugfixes including a fix for theskrll5-22/+21
format string vulnerability described in http://www.securityfocus.com/bid/3498 Closes pkg/15149 from <naoki@fukaumi.org>
2001-12-10Added optional GSSAPI support. To activate this feature, please setmartti4-24/+19
SASL_USE_GSSAPI=YES in /etc/mk.conf
2001-12-04By default, prevent invocation of GNU "auto*" driven by the generatedjlam1-2/+1
Makefiles during the build process by touching various auto{conf,make} source files to make them up-to-date. Packages that require regenerating the configure script and Makefile.in files should make the appropriate calls to auto{conf,make} in a pre-configure target. This allows the various targets listed in ${_CONFIG_PREREQ} to modify the generated files without triggering the GNU auto* tools and having the modifications be overwritten.
2001-12-02bsd.pkg.install.mk calls the INSTALL script at the right timesjlam1-3/+1
automatically, so no need to do it ourselves.
2001-11-29Get rid of manually adding "nbX" to PKGNAME when a pkg was changed inhubertf1-2/+2
pkgsrc. Instead, a new variable PKGREVISION is invented that can get bumped independent of DISTNAME and PKGNAME. Example #1: DISTNAME= foo-X.Y PKGREVISION= Z => PKGNAME= foo-X.YnbZ Example #2: DISTNAME= barthing-X.Y PKGNAME= bar-X.Y PKGREVISION= Z => PKGNAME= bar=X.YnbZ (!) On subsequent changes, only PKGREVISION needs to be bumped, no more risk of getting DISTNAME changed accidentally.
2001-11-26Use PKG_{USERS,GROUPS} instead of PKG_{USER,GROUP}.jlam2-7/+7
2001-11-26Forgot a CONFDIR -> PKG_SYSCONFDIR replacement.jlam1-2/+2
2001-11-26Missed a CONFDIR -> PKG_SYSCONFDIR replacement.jlam1-2/+2
2001-11-25PKG_SYSCONFDIR is where the configuration files for a package may be found.jlam1-2/+2
This value may be customized in various ways: PKG_SYSCONFBASE is the main config directory under which all package configuration files are to be found. PKG_SYSCONFSUBDIR is the subdirectory of PKG_SYSCONFBASE under which the configuration files for a particular package may be found. PKG_SYSCONFDIR.${PKGBASE} overrides the value of ${PKG_SYSCONFDIR} for a particular package. Users will typically want to set PKG_SYSCONFBASE to /etc, or accept the default location of ${PREFIX}/etc. This obsoletes the use of CONFDIR, which was active for only 6 days, so no need to have a workaround to still accept old CONFDIR settings.
2001-11-21Buildlinkify, respect ${CONFDIR}, use general INSTALL/DEINSTALL scripts,jlam6-204/+136
and make sasl_passwd into a real rc.d script.
2001-11-01Move pkg/ files into package's toplevel directoryzuntum7-6/+6
2001-10-18SVR4 packages have a limit of 9 chars for a package name.veego1-1/+2
The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-13 06:05:43 +0000