[[PageOutline]] = Trust anchors for GENI aggregates = This page lists various trust anchors which GENI aggregates can use. There's a section for the authorities that the GPO recommends for all GENI aggregates, and a second section for authorities which some aggregates may want to trust in unusual circumstances. A note on certificate types: * A self-signed SA certificate can be added to an aggregate's list of trusted certificates by itself --- it contains everything the aggregate needs in order to trust that slice authority * MA and CA certificates for a host can be used as a pair --- the MA certificate signs certificates presented by individual experimenters, while the CA is the self-signed certificate needed to complete the chain to a trust root. For most GENI aggregates, you need only install the CA cert, and the entire chain will be trusted. However, we provide the MA cert as well in case any aggregates need both, and installing both should be harmless. = Recommended GENI slice authorities = As of March 2013, the GPO recommends that all GENI aggregates trust the following GENI slice authorities (aka "the GENI cert bundle"), allowing the users at those SAs to use resources at GENI racks, GENI backbone and regional networks, etc. The table below includes links to the SA certificate file, or to both of the MA and CA certificates, for each trust anchor. You can also download the entire bundle as a [attachment:geni-cert-bundle.tar.gz compressed tar file], which unpacks into a directory named "geni-cert-bundle", and includes an MD5SUMS file with md5sums for the certs. The md5sum for the .tar.gz file itself is c21e69e57ce3868d4edc302899ffc9f7. || '''Description''' || '''Hostname''' || '''Certificate type''' || '''Certificate Expiration''' || '''File/Checksum''' || || GENI clearinghouse || ch.geni.net || CA (self-signed) || 2018-05-19 || [attachment:ch.geni.net-ca.pem 40c979b9477822f353027ab91dc7a296] || || GENI clearinghouse || ch.geni.net || MA (signed by CA) || 2018-05-19 || [attachment:ch.geni.net-ma.pem ffc8b06bd198a429245f7ef9eedaa3fb] || || Utah ProtoGENI || emulab.net || SA (self-signed) || 2015-05-25 || [attachment:emulab.net.pem e9e6389938d71fed6ab8d667ac91f60a] || || !PlanetLab Central || planet-lab.org || SA (self-signed) || 2016-09-04 || [attachment:plc.pem 4f0182127f4d4dc3c553d9d4a9a1a825] || Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate. = Other GENI slice authorities = Most aggregates will not want to trust the following additional slice authorities, but there may be some unusual circumstances where some might. The GPO '''does not recommend that GENI aggregates trust these authorities''' except when there's a specific concrete reason for a particular aggregate to do so. The table below includes links to the SA certificate file, or to both of the MA and CA certificates, for each trust anchor. || '''Description''' || '''Hostname''' || '''Certificate type''' || '''Certificate Expiration''' || '''File/Checksum''' || || GPO staging clearinghouse || ch1.gpolab.bbn.com || CA (self-signed) || 2018-06-11 || [attachment:ch1.gpolab.bbn.com-ca.pem 8a5e7c9194522ec79c6db2efeaa44569] || Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate.