Note: This web site is only kept up to date for OSG Software 1.2 (VDT 2.0.0). If you are looking for information for the most recent release, the RPM-based OSG Software 3.0, please see the OSG documentation web site

Globus 2.4 vs. Globus 3.2

We are working hard to provide you with the latest versions of individual packages in the VDT. VDT 1.3.0 is based on the pre-web services components of the newer Globus 3.2 series. We have retained some of the 1.2 series patches in VDT 1.3.0 and included a couple of new patches.

New features in Globus 3.2

In addition to a number of bug fixes, Globus 3.2 also contains several new features. For a complete list see the Globus 3.2.0 release notes and the Globus 3.2.1 release notes.

Compatibility issues

Most people will have no problem transitioning from Globus 2.4 to 3.2. Our internal certification tests needed no changes for Globus 3.2 and we were able to submit from a Globus 2.4 client to 3.2 server and vice versa without any difficulty.

However, a small change in GSI will impact some users. Previous versions of GSI were based on the OpenSSL 0.9.6 series. Globus 3.2 has switched to OpenSSL 0.9.7. While this upgrade brings additional security, it will also change how some certificate DNs are reported. This only applies to you if the subject of your certificate, the host certificate of a grid resource you use or the certificate of the CA that signed one contains an email address. This will effect the following CAs distributed by the VDT:

For example, the DN of the UK e-science CA used to be:
C=UK, O=eScience, OU=Authority, CN=CA/
In Globus 3.2 this becomes:
C=UK, O=eScience, OU=Authority, CN=CA/

Problems caused by remote host certificates or signing CAs can be fixed by using the CA-Certificates package provided by VDT 1.3.0. However, those same certs can not be used by Globus 2.4 clients.

If your grid-mapfile contains any certificates with email addresses in their subject you'll need to change Email= to emailAddress= after upgrading to Globus 3.2.