Commit graph

13 commits

Author SHA1 Message Date
jmc
9ba4361a12 Nuke definition for INSTALL_EXTRA_TMPL here since INSTALL doesn't exist. 2003-09-02 23:14:44 +00:00
jlam
b2677a2cb0 Add definitions for DEINSTALL_EXTRA_TMPL and INSTALL_EXTRA_TMPL if
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-08-30 22:51:11 +00:00
recht
a4ec41985a Update to 2.1.15.
changes:
Fix build on NetBSD-current with OpenSSL 0.9.7.

New in 2.1.15
-------------
* Fix a number of build issues
* Add a doc/components.html that hopefully describes how things
  interact better.

New in 2.1.14
-------------
* OS X 10.2 support
* Support for the Sun SEAM GSSAPI implementation
* Support for MySQL 4
* A number of build fixes
* Other minor bugfixes

OK'ed by chris@
2003-08-16 09:06:41 +00:00
jlam
cc05368605 Rearrange the Makefile logic so that we can easily create Cyrus SASL 2.x
plugin packages.
2003-03-19 22:25:05 +00:00
seb
3869278076 Update to version 2.1.12.
New in 2.1.12
-------------
* Distribute in Solaris tar (not GNU tar format)
* Fix a number of build/configure related issues.

New in 2.1.11
-------------
* Add the fastbind auth method to the saslauthd LDAP module.
* Fix a potential memory leak in the doors version of saslauthd.
* NTLM now only requires one of LM or NT, not both.
* Fix a variety of Berkeley DB, LDAP, OpenSSL, and other build issues.
* Win32 support compiles, but no documentation as of yet.
2003-02-27 13:18:06 +00:00
jlam
d7f69e47ce Instead of including bsd.pkg.install.mk directly in a package Makefile,
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-28 22:03:00 +00:00
chris
9b2c204ebc Update cyrus sasl to 2.1.10. As noted in pkg/19335.
Fixes a buffer overflow:
http://online.securityfocus.com/archive/1/302603

and other misc bugs.

(note .sig file checked and verified)
2002-12-11 23:48:58 +00:00
chris
8f034dce82 Match the default for the sasl socket dir, IE /var/run/saslauthd.
Also the dir is now root owned, but with 755 permissions, previously it was
cyrus owned.

Bump PKGREVISION to 2.
2002-11-23 14:44:53 +00:00
seb
3258c54477 Bump PKGREVISION:
- No need for /usr/lib/sasl2 anymore: INSTALL script removed, DEINSTALL
  script tuned.
- Removed auto* tools dependencies by providing patch files for generated
  configure and Makefile.in.
- Use ${PKGDIR} instead of ${.CURDIR} for PLIST_SRC files.
- `--with-rc4' does not need an argument.
- Use BUILDLINK_PREFIX.whatever instead of BUILDLINK_DIR.
- Fix GSSAPI build for non-current NetBSD, this includes patch-ag removal.
- Fix PLIST handling by providing PLIST.post (lib/sasl2 removal at deinstall
  time) and fixing PLIST.common (include/sasl removal at deinstall time).
- Bump BUILDLINK_DEPENDS.cyrus-sasl in buildlink2.mk.
- Work around problem introduced by LTCONFIG_OVERRIDE and direct usage
  of ac_cv_can_build_shared in configure.in as suggested by Nick Hudson.
  Remove patch-ab (sasl-config is gone btw, it was not needed anyway).
  This should fix plugins shared libs problem as reported -among other-
  in PR pkg/19001 by Stephen Degler <sdegler at degler dot net>.
2002-11-14 22:21:13 +00:00
chris
449b9f7388 Make it build again if you don't have SASL_USE_GSSAPI set anywhere. 2002-11-13 10:44:26 +00:00
chris
418f424ad3 Fix support for kerberos 5, it now compiles and installs properly when
SASL_USE_GSSAPI is defined to yes.  Note untested as I don't have kerberos
setup, it probably won't work until some patches are put in to fix plugins
not working.
2002-11-13 10:39:12 +00:00
seb
cdf4db798b Remove gmake dependency. 2002-10-27 23:32:36 +00:00
chris
ce6ee05b60 Initial import of cyrus-sasl 2.1.9.
This is the latest release of cyrus-sasl.  It is needed for the 2.1.x
versions of cyrus-imapd.

SASL is a method for adding authentication support to connection-based
protocols.  To use SASL, a protocol includes a command for identifying and
authenticating a user to a server and for optionally negotiating protection
of subsequent protocol interactions.  If its use is negotiated, a security
layer is inserted between the protocol and the connection.
2002-10-27 15:08:59 +00:00