summaryrefslogtreecommitdiff
path: root/security/cyrus-sasl2
AgeCommit message (Collapse)AuthorFilesLines
2004-11-25These packages install libraries that dlopen() shared modules.jlam1-1/+4
2004-11-15Update security/cyrus-sasl2 and associated plugins to 2.1.20. Changesjlam15-198/+127
from version 2.1.19 include: * Fixes to cram plugin to avoid attempting to canonify uninitialized data (This removes the need for patch-af). * NTLM portability fixes. * Avoid potential attack using SASL_PATH when sasl is used in a setuid environment. * A trivial number of small bugfixes.
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-7/+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-09-12List the other cy2-* packages that use cyrus-sasl2/Makefile.common.jlam1-1/+7
2004-08-13Split out the plugins into individual packages. This allows us tojlam6-111/+49
explicitly add only those plugins for SASL support for servers that won't let us exclude any found SASL plugins. Also, don't bother building the static library since the static library is useless until the build mechanism is fixed by the Cyrus maintainers. Bump the PKGREVISION.
2004-08-06There is no way for libtool to generate a convenience library thatjlam6-3/+145
can be used to create shared libraries _and_ be linked into a statically linked program. Instead of trying to hack libtool to do this, just accept the fact and do what you want another way! Remove the ugly hack in sasldb/Makefile.am that regenerated the static archive from the non-PIC object files. While this was fine for linking into programs, it breaks things when you link this into the sasldb plugin. Leaving it the other way, where the static archive from the PIC object files, is also unacceptable because there are potential problems on some platforms when linking an archive of of PIC objects into an executable. The solution: let the static archive contain PIC objects and be used to link into the sasldb plugin, but for the programs in the utils directory, explicitly add the non-PIC object files listed in $(SASL_DB_BACKEND_STATIC) to the files used to generate the programs. This is easy because SASL_DB_BACKEND_STATIC is already generated properly by config/sasldb.m4, so make use if it. This should fix problems with using Cyrus SASL on non-i386 platforms noted in PR pkg/26492 by Matt Dainty. Bump the PKGREVISION.
2004-08-05Rename Makefile.options to options.mk in the packages that I maintain.jlam2-3/+3
This follows the example of the mail/dovecot package, as suggested by <schmonz>.
2004-08-04Updated security/cyrus-sasl2 to 2.1.19. Changes from version 2.1.18jlam11-94/+42
include: * Support for forwarding of GSSAPI credentials * A nontrivial number of small bugfixes.
2004-08-03Become the maintainer for this package (approved by <chris>).jlam1-2/+2
2004-07-30Convert to use bsd.options.mk. The relevant options variable to setjlam5-49/+72
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-08Use a better fix from ASG CVS the GSSAPI problems.recht3-10/+49
patch-ap now includes the updates between rev 1.84 and rev 1.90 modulo the support for passing of GSSAPI credentials. Patch provided by Jukka Salmi in PR 26184 Bump PKGREVISION to 3 for the new fix.
2004-07-06Refer to ${VARBASE} instead of /var for the location for local statejlam2-4/+4
information.
2004-07-06Re-add revision 1.3 of patch-ab as patch-ag. This resurrects a change tojlam3-3/+17
use shlibtool to build the plugins to avoid generating and installing a static archive for the plugin module. This fixes PLIST breakage. Bump the PKGREVISION to 2.
2004-07-05Pull in a fix from ASG CVS: increase maxoutbuf buffer sizerecht3-2/+17
This allows uploading of SIEVE scripts larger than 4kb if GSSAPI authentification is used for cyrus-imapd. link to the patch provided by Jukka Salmi in PR 26165 bump PKGREVISION to 1
2004-05-16add USE_GNU_TOOLS+=make so that libsasldb.a gets built correctly.danw1-1/+2
(Nothing in the build actually uses the static version of the library, and it doesn't get installed either, so this has no effect beyond making the build not bomb out on Darwin, pkg/25575).
2004-05-09Unused.wiz1-20/+0
2004-03-29Update security/cyrus-sasl2 to 2.1.18. Changes from version 2.1.17jlam16-110/+134
include: * Better error-handling. * Support for Courier-IMAP authdaemond for plaintext password verification. * Fixed resource leaks and buffer overruns. pkgsrc changes include: * SASL_DBTYPE is either "ndbm" or "berkeley" and sets the db format of the sasldb authentication database, defaulting to ndbm. * SASLSOCKETDIR is the location of the saslauthd socket directory. * AUTHDAEMONVAR is the localt of the authdaemond socket directory. * SASL_ENTROPY_SOURCE is a file of random bytes used as a PRNG. This closes PR 24649 and PR 24694.
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-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-2/+4
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-02-17We no longer need to set GNU_MISSING_OVERRIDE after the changes in revisionjlam1-3/+1
1.27 of tools.mk to hide the auto* tools between pre-configure and do-configure.
2004-02-14LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globsjlam1-2/+1
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that are automatically handled by the default setting in bsd.pkg.mk.
2004-02-14Add a note to cyrus-sasl2/Makefile.common about which package Makefilesjlam1-1/+7
include it. This is a reminder to anyone who updates cyrus-sasl2 to also touch the other packages. Update the cy2-*/PLIST files to have the correct module version numbers.
2004-02-14CONFIG_STATUS_OVERRIDE is the default in bsd.pkg.mk, so no need for thesejlam1-3/+1
definitions here.
2004-02-14Remove unused patch.jlam1-198/+0
2004-02-14Don't try to link GSSAPI module staticly if we're using shared libs.jlam7-15/+92
Fixes undefined symbols on linking other software against libsasl2. Bump PKGREVISION.
2004-02-14Update security/cyrus-sasl2 to 2.1.17. Changes from version 2.1.15 include:jlam16-267/+92
* Now correctly do authorizaton callback in sasl_checkpass() * Writable auxprop support * Significantly improved documentation
2004-02-12Remove hidden dependency on autoconf by using GNU_MISSING_OVERRIDE. Also,jlam2-3/+5
PKGSHLIBTOOL has been removed from pkgsrc and we're supposed to use ${SHLIBTOOL} instead.
2004-01-27Use $FIND with "-print". Noted by Georg Schwarz in PR pkg/24248heinz1-2/+2
2004-01-24Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. Injlam1-2/+2
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched.
2004-01-21Recognize KERBEROS as a flag that can cause this package to be built usingjlam1-2/+3
Kerberos for GSSAPI support.
2004-01-21Remove debugging line accidentally committed in previous.jlam1-2/+1
2004-01-21Convert to use krb5.buildlink3.mk to get Kerberos 5 support. Tested tojlam1-6/+5
build and install properly using Heimdal.
2004-01-09Remove references to saslauthd from this package.jlam2-46/+1
2004-01-09Provide uint*_t datatypes for UINT* typedefs by including eitherjlam6-28/+74
<stdint.h> or <inttypes.h>. Fix suggested by the analysis in pkg PR 22031.
2004-01-09Update cyrus-sasl2 to 2.1.15nb2. Changes from version 2.1.15nb1 arejlam9-84/+40
splitting out the saslauthd daemon into a separate package, security/cyrus-saslauthd. This allows the saslauthd daemon to support additional database backends for plaintext authentication without adding unrelated dependencies to the cyrus-sasl2 package.
2004-01-08bl3ifyjlam2-13/+18
2004-01-05Fix build if SASL_USE_GSSAPI=YESmarkd3-10/+38
From PR pkg/23634 by Louis Guillaume. also noted in PR pkg/23339. Fix configure to not try and _statically_ link in gssapi support as it doesn't work (unresolved symbols when used). This deals with the second part of PR pkg/23339.
2004-01-05Use S/+$// instead of C/\+$// to save a backslash. Very highlyjlam1-2/+2
recommended by seb :)
2004-01-04Re-arrange to match example buildlink3.mk file in bsd.buildlink3.mk.jlam1-9/+6
2004-01-03Initial sprinkling of work-in-progress buildlink3.mk files for using thejlam1-0/+19
buildlink3 framework.
2003-12-15Expand ROOT_USERmartti1-1/+2
2003-11-21Install the saslauthd manpage as cat8/saslauthd.0 as it should be on BSDjlam4-3/+66
systems.
2003-11-21s/root/@ROOT_USER@/ to be more generally correct.jlam1-2/+2
2003-11-12PKGREVISION++ after openssl update.jschauma1-1/+2
2003-10-06Bump revision.christos1-1/+2
2003-10-06regenchristos1-2/+2
2003-10-06Fix uninitialized variable that caused core-dumps.christos1-3/+13
2003-10-05Add BUILD_DEFS line for USE_PAM and SASL_USE_GSSAPI.chris1-1/+3
2003-10-03Some xargs (Hi Sun) run the command even when stdin is "empty". Compareseb1-2/+2
'echo | xargs echo' on NetBSD and Solaris... Workaround this in post-extract target's 'rm' by adding a '-f' argument to it. XXX Current upstream tarball does not have .orig files, I could have removed this post-extract target...
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-18 03:34:59 +0000