Difference between revisions of "SHA-2 support middleware baseline"
Jump to navigation
Jump to search
Line 91: | Line 91: | ||
|- | |- | ||
|VOMS | |VOMS | ||
|UMD-2 | |UMD-2 (version 2.0.9) | ||
|'''UMD-3''' | |'''UMD-3''' | ||
|- | |- |
Revision as of 17:51, 13 March 2013
This page contains the status of SHA-2 signed certificates support for the middleware products. Please note that:
- The table is based mostly on the information reported by the product teams, and on the results of the tests performed during the UMD software provisioning process, you can find a summary of the test results in this page.
- Some products supported RFC and SHA-2 certificates in versions prior to UMD-2. UMD-1 is ending the security support, therefore the minimum release reported in the table is UMD-2
Product name | First product version (or UMD major release) supporting SHA-2 | First product version (or UMD major release) supporting RFC proxies |
---|---|---|
Argus | UMD-2 | UMD-2 |
ARC-CE | UMD-2 | UMD-1 |
ARC-Clients | UMD-2 | UMD-1 |
ARC-Infosys | UMD-2 | UMD-1 |
ARC-CORE | UMD-2 | UMD-1 |
ARC-Gridftp | UMD-2 | UMD-1 |
CREAM | UMD-3 | UMD-2 |
dCache | UMD-3 | UMD-2 |
DPM | UMD-2 | UMD-2 |
FTS | UMD-2 | UMD-2 |
gLExec | UMD-2 | UMD-2 |
Gridsite | UMD-2 | UMD-2 |
LB | UMD-2 | UMD-2 |
lcg-utils | UMD-2 | UMD-2 |
LFC | UMD-2 | UMD-2 |
Proxy renewals | UMD-2 | UMD-2 |
Pseudonimity | UMD-3 | UMD-3 |
StoRM | UMD-3 | UMD-2 |
Trustmanager | UMD-2 | UMD-2 |
UNICORE | UMD-2 | UMD-3 |
VOMS | UMD-2 (version 2.0.9) | UMD-3 |
WMS | UMD-2 | UMD-3 |
- To report of errors or missing information, please contact operations@egi.eu, thanks.