Changelog since previous version in pkgsrc
crusdesaml-1.8 2017-05-26
Fix crash introduced server side in 1.6 for saml_log()
crusdesaml-1.7 2017-05-22
Only iterate on XML_ELEMENT_NODE nodes
crusdesaml-1.6 2017-05-20
Typos in man pages (Florian Best)
Don't log the password length if it is too small (Florian Best)
Stop if wxmlXPathRegisterNs failed (Florian Best)
autoconf: Remove duplicate $(DESTDIR) (Florian Best)
PAM: Require only one provider (Florian Best)
PAM: No SONAME versioning (Philipp Hahn)
autoconf: Only strictness foreign (Philipp Hahn)
PAM: fix static PAM module build (Philipp Hahn)
Hide internal symbols (Philipp Hahn)
Fix varadic function SIGSEGV (Philipp Hahn)
Fix crash when using saml_log()/saml_error() in SASL client plugin
crusdesaml-1.5 2012-11-13
mod_shib2 compatibility, debug messages (Jan Tomasek)
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.
PAM provides a way to develop programs that are independent of
authentication scheme. These programs need "authentication modules" to be
attached to them at run-time in order to work. Which authentication module
is to be attached is dependent upon the local system setup and is at the
discretion of the local system administrator.
This package contains a SASL plugin and a PAM module that perform a crude
check on a SAML authentication assertion. The assertion signature and date
are verified, and access is granted on behalf ot the user taked for a
onfigurable attribute.
The only protection against replay attacks is the assertion validity dates
checks, this authentication is therefore secure only if the SAML
authentication assertion remains secret. The assertion has the same role
as a web cookie used for authentication.
