Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Revision as of 13:22, 3 October 2016 by Jpina (talk | contribs) (→‎Under Staged Rollout)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search




  • keystone-VOMS to be included in CMD-OS, working on CMD-OS "0" (pilot release for testing purposes)
  • going to describe the process here for TPs
  • preparing October release: DPM, ARC, lcmaps, Globus, GFAL, VOMS-admin-server, ARGUS,
  • UMD3 canL/gridsite release, preparing release (now on Vincenzo, in progress)

Status of the products verification/staged rollout

Ready to be Released


  • Canl 2.2.7
  • Gridsite 2.3.2


  • Canl 2.2.7
  • Gridsite 2.3.2
  • Xroot 4.3.0
  • Gfal2 2.11.1
  • gfal2-utils 1.3.2
  • gfal2-python 1.8.4
  • gfal2-python 1.8.4

Under Staged Rollout

  • dpm 1.8.11
  • myproxy 6.1.18
  • gridftp 10.4.
  • globus-default-security 6.3.0
  • davix.sl6.x86_64-0.6.3
  • voms-admin-server 3.5.0
  • Voms 2.0.14
  • arc 15.03.9

In Verification

  • lcmaps-plugins-vo-ca-ap 1.2.3
  • gram5 13.13.0
  • argus 1.7.2
  • arc 15.03.9

Report from WLCG MW Officer


Updates from Technical Providers



We did some tests with DPM-DSI 1.9.8-3 + latest globus compiled with openssl 1.1.0 released in EPEL-testing by Mattias . Everything looks ok

Data management clients







As previously announced, the Globus Toolkit has been updated to work with the recently released OpenSSL 1.1.0. These updates have now been packaged in EPEL.

EPEL 5, 6 and 7 of course have not updated their OpenSSL versions. But in order not to have to maintain different versions of the Globus Toolkit codebase the changes for OpenSSL 1.1.0 have been done in a backward compatible way so that the new code compiles with the older OpenSSL version used in EPEL as well. The support for some really old versions of OpenSSL was dropped.

Some very low level parts of the code required significant changes, since some deprecated APIs in OpenSSL were removed an also because many of openssl's scructs are now opaque and can only be manipulated using setter and getter functions. The API and ABI of the Globus Toolkit libraries should however remain unchanged.

A few points to highlight:

Since all versions of OpenSSL that are now supported by the Globus Toolkit support the proxy certificate info extension, the implementation of this extension in the globus-gsi-proxy-ssl library, i.e. the PROXYCERTINFO type and the associated functions, has been deprecated in favour of the OpenSSL implementation (i.e. the PROXY_CERT_INFO_EXTENSION type). The PROXYCERTINFO type still exists and code that use it and the associated functions will compile (with a warning), and existing binaries will still work.

Another thing to look out for is if you are using the functions

- globus_gsi_proxy_handle_get_proxy_cert_info
- globus_gsi_proxy_handle_set_proxy_cert_info

in the globus-gsi-proxy-core library. These are now implemented using PROXY_CERT_INFO_EXTENSION rather than PROXYCERTINFO. However, both implementations are available in the new library which now uses versioned symbols. This means that existing binaries that were compiled against an older version of the library will still use the PROXYCERTINFO implementation, while new compilations get the PROXY_CERT_INFO_EXTENSION version by default. If you for some reason need the PROXYCERTINFO versions of the functions when compiling against the new library they are available as:

- globus_gsi_proxy_handle_get_proxy_cert_info_proxy_ssl
- globus_gsi_proxy_handle_set_proxy_cert_info_proxy_ssl

In the globus-gssapi-gsi library there is a new implementation of the gss_get_mic and gss_verify_mic functions. Testing has shown these new implementations to not be fully backward compatible, which causes some problems for the gsissh client/server authentication. There is an option in the gsi.conf file whether to use this new implementation or not. For now an update to the package has been created that changes the default back to using the old implementation where possible. However, the old implementation can not be used when building against openssl 1.1.0, so this issue will have to be addressed in the future.

The updates are available in EPEL testing:

Please test and provide feedback.

OpenSSL 1.1.0

OpenSSL 1.1.0 has been proposed for inclusion in Fedora 26:

and the transition in Debian unstable will start soon:





New Preview Repository release on Sep 14th:

  • Preview 1.4.0 (sl6): ARC 15.03 update 9, FTS 3 - 3.4.7 , VOMS clients 3.0.7, VOMS Admin 3.5.0, VOMS 2.0.14 (and more)
  • Preview 2.4.0 (CentOS7): ARC 15.03 update 9, dCache 2.13.42 , edg-mkgridmap 4.0.3 , FTS 3 - 3.4.7 , QCG-Computing 4.0.0 , QCG-Notification 4.0.0 , UI and WN.