The Cyrus SASL (Simple Authentication and Security Layer)
SASL is the Simple Authentication and Security Layer, 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.
===> The following configuration options are available for cyrus-sasl-2.1.28_6:
ALWAYSTRUE=off: Alwaystrue password verifier (discouraged)
AUTHDAEMOND=on: Use of authdaemon
DOCS=on: Build and/or install documentation
KEEP_DB_OPEN=off: Keep handle to Berkeley DB open
LMDB0=on: Use LMDB 0.9 library
OBSOLETE_CRAM_ATTR=on: cmusaslsecretCRAM-MD5 auxprop property
OBSOLETE_DIGEST_ATTR=on: cmusaslsecretDIGEST-MD5 auxprop property
OPIE=off: Use OPIE with OTP
SASLDB_IN_VAR=off: sasldb in /var/db/sasl2
====> Options available for the group PLUGIN
ANONYMOUS=on: ANONYMOUS authentication
CRAM=on: CRAM-MD5 authentication
DIGEST=on: DIGEST-MD5 authentication
LOGIN=on: LOGIN authentication
NTLM=on: NTLM authentication
OTP=on: OTP authentication
PLAIN=on: PLAIN authentication
SCRAM=on: SCRAM authentication
====> SASLdb auxprop plugin: you can only select none or one of them
BDB1=on: Berkeley DB 1.85 support
BDB=off: Berkeley DB support
GDBM=off: GNU dbm library support
LMDB=off: OpenLDAP Lightning Memory-Mapped Database support
===> Use 'make config' to modify these settings
databases/lmdb0: Add port for LMDB 0.9.x legacy ABI
LMDB 1.0 introduced an incompatible on-disk format change and subtle
API breakage: applications that compiled cleanly against 1.0 headers
could fail silently at run time. Known affected ports include dns/knot3,
mail/bogofilter, and mail/postfix; the postfix issue has been confirmed
upstream. Linux distributions such as Arch Linux have observed the same
breakage. Samba can also be affected in certain configurations.
Because the regression is not detectable in an -exp build run -- the
postfix failure only manifests at run time, and bogofilter was caught
only because post-build self-tests happen to exercise this path -- we
cannot rely on package builds to validate the 1.0 upgrade.
This commit introduces databases/lmdb0 as a holding port for the 0.9.35
(Only the first 15 lines of the commit message are shown above )
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
security/cyrus-sasl2: respect CFLAGS
Currently CFLAGS are not respected, which may result in various crashes, e.g.
CPUTYPE is not respected, which results in SIGILL on QorIQ E5500 CPU.
Reported by: AmigaBSD (on #powerpc64 IRC)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
security/cyrus-sasl2{,-saslauthd}: lmdb did not work for postfix
- sasldb2-lock requires write permission for mail group
- introduce SASLDB_IN_VAR option which places sasldb into /var/db
Reported by: Herbert J. Skuhra <herbert@gojira.at>
security/cyrus-sasl2: unbreak building with stock OpenSSL for stable/11
Sendmail bundled with FreeBSD has SASL support and the Handbook tells
how to rebuild the Sendmail with SASL enabled if you have installed
cyrus-sasl2 that links with OpenSSL's libcrypto.
Sendmail uses old OpenSSL 1.0.2 API, so cyrus-sasl2 should be built
with stock libcrypto even if newer OpenSSL is installed for Ports.
This change adds new option SSL to the port (enabled by default).
If disabled, cyrus-sasl2 is built witch stock libcrypto not depending
on ports version of OpenSSL.
PORTREVISION not changed as default build is not affected.
Update `databases/gdbm' to version 1.18.1, an important bugfix release
which restores compatibility with old databases (version 1.8) and some
later versions which were built without mmap(2) support. Due to shlib
version change, bump port revisions of the consumer ports.
PR: 233059
Exp-run by: antoine
Approved by: maintainer (johans, numerous timeouts)
Add OpenSSL 1.1.0 support for saslauthd.
There are the patches to support OpenSSL 1.1.0 in cyrus-sasl2
port, already. But, it was incomplete for saslauthd.
PR: 231647
Submitted by: dewayne [...] heuristicsystems.com.au (with some modifications)
Remove support for variables that have been deprecated for a while.
variables deprecation revision
WITHOUT_NLS 2013-12-13 r336337
WITH_/WITHOUT_ 2014-02-24 r345870
NOPORT(DOC|EXAMPLE)S 2014-04-19 r351587
WITH_BDB_VER 2016-05-02 r414444
OVERRIDE_LINUX_BASE_PORT 2016-09-05 r421387
WITH_OPENSSL_(BASE|PORT) 2016-06-16 r416965
While there, add an ERROR variable that works like DEV_ERROR, but for
user facing errors, and move NOPORTDOCS,
NOPORTEXAMPLES and WITHOUT_NLS to it.
Cleanup bsd.sanity.mk a bit.
Fix fallout.
PR: 224613
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D13490
security/cyrus-sasl2: separate sql plugins into security/cyrus-sasl2-sql
Fix circular-dependency problem happens after SASL/LDAP was added as
plugin to mysql57-client in r446496
Reviewed by: bapt, mat (mentor), ume (maintainer)
Approved by: mat (mentor), ume (maintainer)
MFH: 2017Q3
Differential Revision: https://reviews.freebsd.org/D11805
Remove USE_SQLITE from bsd.databases.mk, replaced by USES=sqlite.
While there replace USE_SQLITE=x by USES=sqlite:x.
PR: 208971
Submitted by: mat
Exp-run by: antoine
With hat: portmgr
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D5951
Bump more ports that depend on libsqlite3.so:
- ports that set USE_SQLITE with the *_USE option helper
- ports that depend on libsqlite3 indirectly as reported by pkg rquery
Approved by: portmgr (implicit)
- Keep .la files for now and delete a libtool patch. [1]
- Replace a Makefile.in patch with USES=pathfix.
Reported by: Willy Offermans <Willy@Offermans.Rompen.nl> [1]
A postscript was added to pkg-messase so that those who
need them for existence of cyrus-sasl2-gssapi and
cyrus-sasl2-ldapdb might notice.
Spotted by: zi
SASL GSSAPI authentication plugin is divided into port
different from cyrus-sasl2.
Spotted by: Erick Turnquist <jhujhiti__at__adjectivism.org>,
Scot Hetzel <swhetzel__at__gmail.com>
Fix broken get_fqhostname() logic. Without that fix mail/mutt-devel
compiled with WITH_MUTT_CYRUS_SASL2 option is not able to
connect to IMAPS mailbox.
PR: 161890
Submitted by: novel (myself)
Approved by: maintainer timeout (more than 4 months)
Obtained from: https://bugzilla.cyrusimap.org/show_bug.cgi?id=3589
Feature safe: yes
- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS)
- Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead
PR: 157936
Submitted by: myself
Exp-runs by: pav
Approved by: pav
Backout previous commit.
Unfortunately, it broke GSSAPI when using heimdal in base.
I have no idea how to detect whether heimdal is in base or
from ports, now.
Feature safe: yes
