gLite > gLite 3.1 > glite-VOMS_oracle > Update to glite-VOMS_oracle 3.1.17-0  
 
 

 

 

gLite 3.1

glite-VOMS_oracle - Update to version 3.1.17-0


Date 16.12.2008
Priority Normal

Description

The following fixes are released with glite-VOMS_oracle 3.1.17-0:

1. Upgrade of lcg-vomscerts-5.2.0:

- renamed all certificates with ".pem" suffixes because of bug 43395.
- removed expired certificate of voms.cern.ch

2. Update of glite-security-trustmanager rpm to have the right bouncycastle dependency.

This is a simple fix for the bouncycastle libraries moved to a new location with bouncycastle 1.41. If the lcg CE is working, this change has no effect. When the lcg CE is next time reconfigured or if there is a clean install this change has an effect and will use the algorithm described in patch 2644. See original submission.

It is recommended to run the config script again to get the additional link to the /usr/share/java/bcprov.jar even though it doesn't exist to prepare for the eventual update to bouncycastle 1.41.

3. Fix for GGUS ticket 44201. WMS do not match jobs which should match. This requires a change in the glue schema.

Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #43395 Request to have voms cert file called <something>.pem
 #45278 Removing Multivalue SE from GlueCESEBind

Updated rpms

Name Version Full RPM name Description
glite-VOMS_oracle 3.1.17-0 glite-VOMS_oracle-3.1.17-0.i386.rpm gLite metapackage (glite-VOMS_oracle)
glite-security-trustmanager 1.8.16-3 glite-security-trustmanager-1.8.16-3.noarch.rpm org.glite.security.trustmanager v. 1.8.16-3
glue-schema 1.3.0-5 glue-schema-1.3.0-5.noarch.rpm glue-schema
lcg-vomscerts 5.2.0-1 lcg-vomscerts-5.2.0-1.noarch.rpm lcg-vomscerts

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)