Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

EGI IGTF Release

From EGIWiki
Revision as of 16:27, 20 June 2016 by Brucelli (talk | contribs) (Changed IGTF name)
Jump to navigation Jump to search

To ensure interoperability within and outside of EGI, the Policy on Approved Certification Authorities defined a common set of trust anchors ("Certification Authorities" or "CAs") that all sites in EGI should install. In short, all CAs accredited to the Interoperable Global Trust Federation under the classic, MICS or SLCS Authentication Profiles are approved for use in EGI. Of course, sites may add additional CAs as long as the integrity of the infrastructure as a whole is not compromised. Also, if there are site or national policies/regulations that prevent you from installing a CA, these regulations take precedence -- but you then must inform the EGI Security Officer (see EGI CSIRT:Main Page) about this exception.

Version 1.74 - change log and information

The change log contains important notices about the release, as well as a list of changes to the trust fabric.

Important Notice for sites in EGI that support WLCG

The WLCG collaboration - having so requested EGI and in line with long-term EGI developments in AAI - has included a specific CA to its own trust anchor distribution. Sites that are also part of WLCG should install BOTH the "egi-core" AND "lcg" meta-packages, according to your policies. Note that your organisation or NGI may also have a specific policy and may have added or removed CAs compared to the EGI core policy. Sites that need compliance with the WLCG policy should install BOTH packages, or you will miss out the CERN WLCG IOTA CA specific exception see EGI document for details and the WLCG statement for the WLCG specific decision.

The EGI production repository contains all relevant packages for both policies (and the WLCG repository contains also all EGI packages). There is no reason to reconfigure repository locations. Specifically installing (adding) also the ca-policy-lcg package may be necessary for system configurations built after May 2009.

Reminder notice for VOMS AA operators

Several updates to this trust anchor distribution incorporate changes to the name of the issuing authority, but the name of the end-entities and the users remains exactly the same. To make the change transparent, all operators of VOMS and VOMS-Admin services are requested to enable the subject-only name resolution mechanisms in VOMS and VOMS Admin


To install the EGI trust anchors on a system that uses the RedHat Package Manager (RPM) based package management system, we provide a convenience package to manage the installation. To install the currently valid distribution, all RPM packages are provided at

The current version is based on the IGTF release with the same version number. Install the meta-package ca-policy-egi-core and its dependencies to implement the core EGI policy on trusted CAs.

Using YUM package management

Add the following repo-file to the /etc/yum.repos.d/ directory:


and then update your installation. How to update depends on your previous activity:

yum clean cache metadata 
yum update lcg-CA 
and you are done. This will update the packages installed to the latest version, and also install the new ca-policy-egi-core package as well as a ca-policy-lcg package. All packages encode the same set of dependencies
  • if you are upgrading from a previous EGI version only, just run
yum update ca-policy-egi-core
although at times you may need to clean the yum cache using yum clean cache metadata
  • if you are installing the EGI trust anchors for the first time, run
yum install ca-policy-egi-core

Using the distribution on a Debian or Debian-derived platform

The 1.39+ releases experimentally add the option to install the trust anchors from Debian packages using the APT dependency management system. Although care has been taken to ensure that this distribution is installable and complete, no guarantees are given, but you are invited to report your issues through GGUS. You may have to wait for a subsequent release of the Trust Anchor release to solve your issue, or may be asked to use a temporary repository. To use it:

  • Install the EUGridPMA PGP key for apt:
wget -q -O - \ \
     | apt-key add -
  • Add the following line to your sources.list file for APT:
#### EGI Trust Anchor Distribution ####
deb egi-igtf core
  • Populate the cache and install the meta-package
apt-get update
apt-get install ca-policy-egi-core

Using the distribution on other (non-RPM) platforms

The trust anchors are provided also as simple 'tar-balls' for installation on other platforms. Since there is no dependency management in this case, please review the release notes carefully for any security issues or withdrawn CAs. The tar files can be found in the EGI repository at

Once you have downloaded the directory, you can unpack all the CA tar,gz as follows to your certificate directory:

for tgz in `ls <ca download dir>`; do tar xzf <ca download dir>/$tgz --strip-components=1 -C /etc/grid-security/certificates; done

Installing the distribution using Quattor

Quattor templates are povided as drop-in replacements for both QWG and CDB installations. Update your software repository (re-generating the repository templates as needed) and obtain the new CA templates from:

Make sure to mirror (or refer to) the new repository at and create the appropriate repository definition file.

For wLCG sites that are migrating from the lcg-CA package: the wLCG policy companion of the EGI templates can be found at (QWG) and (CDB) and can be included in the profile in parallel with the EGI core template. All packages needed are also included in the EGI repository, so only a single repository reference is necessary.

New distribution format (OpenSSL1 dual-hash mode)

The EGI release uses a new format in which to distribute the trust anchors. In OpenSSL version 1.0, as released for example in RedHat Enterprise Linux 6, Fedora Core 12+, or Debian5, the characteristic hash format ("HHHHHHHH.0") has changed. Although it superficially looks the same, each CAs gets a different hash in OpenSSL1 as compared to OpenSSL 0.x, or as compared to BouncyCastle or gLite TrustManager. Please review the EUGridPMA news letter of February 15 for full technical details.

To accommodate this changed hash format, the new distribution uses symbolic links for both hashes, that jointly refer to the same physical file with the CA certificate, called alias.pem. This ensures that the new trust anchor distribution works with both format simultaneously. You can install this distribution on all platforms (both OpenSSL1 as well as OpenSSL0.x) and both are supposed to work.

However, old version of fetch-crl (the 2.x) series will retrieve CRLs for one version of OpenSSL only, namely the version which is used by fetch-crl itself when it is run. To get CRLs downloaded for both versions of OpenSSL

  • run fetch-crl 2.x twice, using a different version of OpenSSL each time. Use the FETCH_CRL_OPENSSL environment variable to specify an explicit OpenSSL version for use by fetch-crl. This is only needed if you actually use both versions of OpenSSL at the same time.
  • upgrade to fetch-crl 3, which has proper dual-hash support as well as many other features. Please refer to for more information on fetch-crl3, or download it from Fetch-crl 3 can also be obtained from your standard OS distribution repository (EPEL, Fedora, Debian).

Patches and work-arounds

mod_ssl renegotiation timeouts

We provide here a workaround for the issue summarised in comment #57 of bug #48458. The following rpm has been added to the repository: dummy-ca-certs-20090630-1.noarch.rpm. Please note that:

  • This rpm is not added to the ca-policy-egi-core, lcg-CA or ca-policy-lcg metapackage dependencies
  • If you want to install it you should run: yum install dummy-ca-certs
  • The RPM contains 60 expired CAs that cannot be used for validation, but will ensure the mod_ssl renegotiation buffer is large enough

For Quattor (QWG and CDB) setups, add


to your templates, preferably in a file different from the automatically-generated egi-ca-policy-core.tpl template.

VOMS-ADMIN server does not start (for VOMS-ADMIN service managers only)

Note: This issue affects only the gLite versions of VOMS-ADMIN (up to version 2.5.5), it does not affect EMI/UMD version of VOMS-ADMIN.

A problem has been found where sites upgraded their VOMS server to the latest version of the trust anchors (CA 1.38) and subsequently the VOMS Administrative Interface (VOMS-ADMIN) fails to start. We are presently working to understand the issue. This does not affect the VOMS server itself, but solely the admin interface.

Please read the full announcement for specific warning and actions that you must take. Changing the repository is not recommended to anyone except for VOMS ADMIN service managers.

The quick fix is for the VOMS server admins to replace the default EGI trust anchor repository by the following temporary repository

which can be configured using the Yum repo file as described in the special documentation.

Concerns, issues and verification

If you experience problems with the installation or upgrade of your trust anchors, or with the repository, please report such an issue through the GGUS system. For issues with the contents of the distribution, concerns about the trust fabric, or with questions about the integrity of the distribution, please contact the EGI IGTF liaison at

You can verify the contents of the EGI Trust Anchor (CA) release with those of the International Grid Trust Federation at, or its mirror at See the IGTF and EUGridPMA web pages for additional information.

Make sure to verify your trust anchors with TACAR, the TERENA Academic CA Repository, where applicable.