Shibboleth is standards-based, open source middleware software which
provides Web Single SignOn (SSO) across or within organizational
boundaries. It allows sites to make informed authorization decisions
for individual access of protected online resources in a
privacy-preserving manner.
This software is a C++ implementation of the Service Provider version 2
component of the Shibboleth can be used in Apache Web servers. The
service provider manages secured resources. User access to resources
is based on assertions received by the service provider (SP) from
an identity provider.
WWW: http://shibboleth.internet2.edu/
===> The following configuration options are available for shibboleth-sp-2.6.1_2:
====> Webserver modules
FASTCGI=off: FastCGI protocol support, e.g. for NGINX
APACHE=on: Build Apache module
====> Optional session storage
ODBC=on: ODBC database backend - store sessions in a database
MEMCACHED=off: Store sessions in memcached
===> Use 'make config' to modify these settings
Shibboleth Service Provider Security Advisory [15 November 2017]
An updated version of the Shibboleth Service Provider software
is available which corrects a critical security issue in the
"Dynamic" metadata provider plugin.
Deployers making use of the affected feature should apply the
relevant update at the soonest possible moment.
Security: b4b7ec7d-ca27-11e7-a12d-6cc21735f730
Add options for fastcgi and memcached and make odbc and apache optional.
Fastcgi allows simple use with NGINX. Memcached is similar to ODBC, in that it
offers another option for more persistent session storage than in-memory.
Update xerces-c3 and shibboleth to latest versions
The update in xerces fixes a buffer overflow security problem that exposes the
possibility of a denial of service attack, and could conceivably result in
remote code execution.
Users of Shibboleth or any other service usingi the xerces-c3 xml library are
recommended to upgrade promptly.
URL: http://xerces.apache.org/xerces-c/secadv/CVE-2016-0729.txt
Security: CVE-2016-0729
Remove UNIQUENAME and LATEST_LINK.
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
Shibboleth SP software crashes on well-formed but invalid XML.
The Service Provider software contains a code path with an uncaught
exception that can be triggered by an unauthenticated attacker by
supplying well-formed but schema-invalid XML in the form of SAML
metadata or SAML protocol messages. The result is a crash and so
causes a denial of service.
You must rebuild opensaml and shibboleth with xmltooling-1.5.5 or later.
The easiest way to do so is to update the whole chain including
shibboleth-2.5.5 an opensaml2.5.5.
URL: http://shibboleth.net/community/advisories/secadv_20150721.txt
Security: CVE-2015-2684
remove @user @group since it does not work with old pkg_tools
[https://wiki.freebsd.org/ports/StageDir] recommends using them, but I see no
point in using both
Reported by: Peter Olsson
Update Shibboleth to 2.5.3, a bug fix release.
Change the cache directory back to the built-in default, /var/cache, and
force mode 755 on that directory. (see r258664 in head why this is a good
thing).
Add odbc support as suggested in ports/189410.
Move /var/cache/shibboleth to /var/db/shibboleth, since /var/cache has mode 750
and cannot be read by the www user. According to hier(7):
db/ misc. automatically generated system-specific database files
so /var/db seems like the best choice
Security update for apache-xml-security-c.
Dependant ports, especially shibboleth2-sp, opensaml2, xmltooling
and log4shib should all be updated.
Security: CVE-2013-2156
Don't remove /var/*/shibboleth with rm -rf, so we don't "pull out the carpet
from underneath" a running shibd. Hence allow updating while the old shibd is
still running.
Update Shibboleth-sp and its tool chain to 2.5.1.
Note that from 2.5, shibd is run as the user shibd. The port tries to fix the
key file ownership but if you have changed the file name of the key from the
default sp-key.pem, make sure you chown your key file(s) to user shibd.
Also, take maintainership of the entire tool chain (approved by all previous
maintainers).
Incorporates the ideas suggested by Craig Leres [177668], making sure that the
ssl key is not added to the package.
PR: 177668, 178694
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.