Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2018-12-09 | Removed commented-out PKGREVISIONs | adam | 1 | -2/+1 | |
2018-04-17 | upgrade to 2.1.27-rc7 so that we can use it with openssl-1.1 | christos | 1 | -2/+2 | |
2017-04-27 | Fix to use PKG_SYSCONFDIR. Bump PKGREVISION for all packages using the | jperkin | 1 | -1/+2 | |
shared Makefile.common. | |||||
2013-04-06 | 'You can use "foo" instead of "${WRKSRC}/foo".' | rodent | 1 | -2/+2 | |
2012-10-23 | Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. | asau | 1 | -3/+1 | |
2008-08-12 | Add DESTDIR support. | obache | 1 | -3/+5 | |
2006-04-18 | Update security/cy2-* plugin packages to code from cyrus-sasl-2.1.21. | jlam | 1 | -2/+1 | |
2006-04-13 | Update path from cyrus-sasl2 to cyrus-sasl. | wiz | 1 | -2/+2 | |
2006-02-05 | Recursive revision bump / recommended bump for gettext ABI change. | joerg | 1 | -1/+2 | |
2005-12-05 | Fixed pkglint warnings. The warnings are mostly quoting issues, for | rillig | 1 | -2/+2 | |
example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html | |||||
2004-12-03 | Rename ALL_TARGET to BUILD_TARGET for consistency with other *_TARGETs. | wiz | 1 | -2/+2 | |
Suggested by Roland Illig, ok'd by various. | |||||
2004-09-22 | Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST. | jlam | 1 | -4/+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-13 | Cosmetic changes. | jlam | 1 | -5/+4 | |
2004-08-08 | Update shared library version. | taca | 1 | -2/+2 | |
2004-08-04 | Updated security/cyrus-sasl2 to 2.1.19. Changes from version 2.1.18 | jlam | 1 | -2/+1 | |
include: * Support for forwarding of GSSAPI credentials * A nontrivial number of small bugfixes. | |||||
2004-03-29 | Update security/cyrus-sasl2 to 2.1.18. Changes from version 2.1.17 | jlam | 2 | -4/+4 | |
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-26 | PKGREVISION bump after openssl-security-fix-update to 0.9.6m. | wiz | 1 | -1/+2 | |
Buildlink files: RECOMMENDED version changed to current version. | |||||
2004-02-14 | Add a note to cyrus-sasl2/Makefile.common about which package Makefiles | jlam | 1 | -2/+2 | |
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-12 | PKGSHLIBTOOL has been removed from pkgsrc; we're supposed to use | jlam | 1 | -2/+2 | |
${SHLIBTOOL} instead. | |||||
2004-01-08 | bl3ify | jlam | 1 | -1/+2 | |
2003-09-13 | Use SHLIBTOOL to install the plugins since we used it to build them. | jlam | 1 | -2/+3 | |
2003-09-13 | * Use LIBTOOL_OVERRIDE instead of LTCONFIG_OVERRIDE. | jlam | 1 | -2/+1 | |
* Use ${SHLIBTOOL} to build the shared plugins so we don't get the useless lib<plugin>.a file. | |||||
2003-08-19 | Update to correct version number on library | jmc | 1 | -2/+2 | |
2003-06-06 | Sync up library versions | jmc | 1 | -2/+2 | |
2003-03-19 | Initial import of security/cy2-login. | jlam | 3 | -0/+37 | |
This is the Cyrus SASL plugin that implements the LOGIN authentication mechanism. It's recommended that it only be used if absolutely necessary since it is not a secure authentication scheme. |