5 | | As of GEC16 (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. |
6 | | |
7 | | 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. |
8 | | |
9 | | Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate. |
| 5 | 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. |
| 24 | Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate. |
| 25 | |
| 26 | = Other GENI slice authorities = |
| 27 | |
| 28 | 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. |
| 29 | |
| 30 | The table below includes links to the SA certificate file, or to both of the MA and CA certificates, for each trust anchor. |
| 31 | |
| 32 | || '''Description''' || '''Hostname''' || '''Certificate type''' || '''Certificate Expiration''' || '''File/Checksum''' || |
| 33 | || GPO staging clearinghouse || ch1.gpolab.bbn.com || CA (self-signed) || 2018-06-11 || [attachment:ch1.gpolab.bbn.com-ca.pem 8a5e7c9194522ec79c6db2efeaa44569] || |
| 34 | |
| 35 | Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate. |