Changes between Version 17 and Version 18 of GeniTrustAnchors


Ignore:
Timestamp:
06/20/18 17:27:22 (4 years ago)
Author:
Hussamuddin Nasir
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTrustAnchors

    v17 v18  
    2323
    2424Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate.
    25 
    26 Older certs (to be removed after 2015-05-25):
    27 || '''Description'''               || '''Hostname'''         || '''Certificate type''' || '''Certificate Expiration''' || '''!File/Checksum'''                                                        ||
    28 || Utah ProtoGENI                  || emulab.net             || SA (self-signed)       || 2015-05-25                   || [attachment:emulab.net.pem e9e6389938d71fed6ab8d667ac91f60a]                ||
    29 
    30 = Other GENI slice authorities =
    31 
    32 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.
    33 
    34 The table below includes links to the SA certificate file, or to both of the MA and CA certificates, for each trust anchor.
    35 
    36 || '''Description'''               || '''Hostname'''         || '''Certificate type''' || '''Certificate Expiration''' || '''!File/Checksum'''                                                        ||
    37 || GPO staging clearinghouse       || ch1.gpolab.bbn.com     || CA (self-signed)       || 2018-06-11                   || [attachment:ch1.gpolab.bbn.com-ca.pem 8a5e7c9194522ec79c6db2efeaa44569]     ||
    38 
    39 Refer to aggregate-specific instructions for how to configure your aggregate to trust a particular certificate.