Difference between revisions of "Middleware products verified for the support of SHA-2 proxies and certificates"
Jump to navigation
Jump to search
Line 161: | Line 161: | ||
|- | |- | ||
| CREAM | | CREAM | ||
| 1.2.1-2 | | 1.2.1-2 | ||
| UMD3? | | UMD3? | ||
! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES | ! align="centre" style="background: none repeat scroll 0% 0% Green;" | YES | ||
! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL | ! align="centre" style="background: none repeat scroll 0% 0% Orange;" | PARTIAL | ||
| RFC proxies do not work using InputSandbox files. '''Workaround: voms-proxy-init -rfc -path_length -1 --voms <VO>''' | | RFC proxies do not work using InputSandbox files. '''Workaround: voms-proxy-init -rfc -path_length -1 --voms <VO>''' | ||
| [https://ggus.eu/tech/ticket_show.php?ticket=93024 GGUS #93024] | | [https://ggus.eu/tech/ticket_show.php?ticket=93024 GGUS #93024] | ||
|- | |||
| WMS | |||
| 3.5.0-5 | |||
| UMD3 | |||
| Not tested yet | |||
! align="centre" style="background: none repeat scroll 0% 0% Red;" | NO | |||
| RFC proxies do not work with WMS 3.5.0-5. | |||
| Open a ticket | |||
|} | |} | ||
[[Category:Middleware]] | [[Category:Middleware]] |
Revision as of 10:08, 16 May 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Starting from January 2013, as part of the UMD quality criteria products requiring authentication are tested for the support of SHA-2. The following tables collects the products tested so far during the UMD software provisioning process.
More information in the SHA-2 support middleware baseline page.
UMD-2
Product name | Version | Released in UMD update # | SHA-2 support | RFC proxies support | Comments | GGUS ticket |
---|---|---|---|---|---|---|
globus-gsissh | 5.5.4 | UMD2.4.0 | YES | YES | ||
DPM | 1.8.6 | UMD2.4.0 | YES | Not tested yet | ||
LFC | 1.8.6 | UMD2.4.0 | YES | Not tested yet | ||
globus-myproxy | 5.9.1 | UMD2.4.0 | YES | Not tested yet | ||
VOMS | 2.0.10 | UMD2.4.0 | YES | NO | VOMS rfc proxies only work with SHA1 user certificates | GGUS #91389 (On Hold until EMI3) |
UI | 2.0.1 | UMD2.3.0 | YES | YES | Available in production | |
globus-GridFTP | 5.2.3 | UMD2.4.1? | YES | Not tested yet | Not available in production yet | |
globus-gsisshterm | 1.3.4 | UMD2.4.1? | NO | YES | Uses a jGlobus version not compatible with SHA2 | GGUS #90815 |
CREAM | 1.1.0-4 | UMD2.4.1 | YES | PARTIAL | RFC proxies do not work using InputSandbox files. Workaround: voms-proxy-init -rfc -path_length -1 --voms <VO> | GGUS #93024 |
UMD-3
Product name | Version | Released in UMD update # | SHA-2 support | RFC proxies support | Comments | GGUS ticket |
---|---|---|---|---|---|---|
VOMS | 3.0.0-1 | UMD3.0.0? | YES | PARTIAL | VOMS rfc proxies work with SHA1 and SHA2 user certificates.
RFC proxies are created but are not usable |
https://savannah.cern.ch/bugs/?101122 |
UI | 3.0.0-1 | UMD3.0.0? | YES | YES |
VOMS rfc proxies work with SHA1 and SHA2 user certificates. NOTE: CREAM 2 is still not compatible with RFC proxies |
|
ARGUS | 1.6.0 | UMD3.0.0? | YES | YES | ||
WN | 3.0.0-1 | UMD3.0.0? | YES | YES | (uses same VOMS clients as UI) | |
LFC | 1.8.6 | UMD3.0.0? | YES | YES | ||
glexec-wn | 1.2.6 | UMD3.0.0? | YES | YES | ||
CREAM | 1.2.1-2 | UMD3? | YES | PARTIAL | RFC proxies do not work using InputSandbox files. Workaround: voms-proxy-init -rfc -path_length -1 --voms <VO> | GGUS #93024 |
WMS | 3.5.0-5 | UMD3 | Not tested yet | NO | RFC proxies do not work with WMS 3.5.0-5. | Open a ticket |