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

 

 

gLite 3.1

glite-VOMS_oracle - Update to version 3.1.20-0


Date 11.05.2009
Priority Normal

Description



glite-FTA_oracle, glite-FTS_oracle, glite-LB, glite-LFC_mysql, glite-LFC_oracle, glite-SE_dpm_disk, glite-SE_dpm_mysql, glite-UI, glite-VOBOX, glite-VOMS_mysql, glite-VOMS_oracle, glite-WMS, glite-WN, lcg-CE

New version of the VOMS Java APIs to fix some bugs. Please, check the list of bugs in the specific service update pages for more information.



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
 #30454 VOMS libraries doesn't use symlink
 #39947 Bug in org.glite.security.voms prevents building of dbgpthr flavors
 #41883 VOMS Java API vulnerability - Fake any role
 #43306 [VOMS]: Memory leak in the api
 #44936 [VOMS 1.8.8-2] VOMS server stops handling requests after 8 hrs
 #45330 Problem with VOMS API Java: for some VOs the .lsc file is not considered
 #46505 "certificate in chain has been revoked" error with voms-api-java
 #47090 VOMS_Init() breaks handling of new-style cert. proxies in Globus libraries

Updated rpms

Name Version Full RPM name Description
glite-VOMS_oracle 3.1.20-0 glite-VOMS_oracle-3.1.20-0.i386.rpm gLite metapackage (glite-VOMS_oracle)
glite-security-voms-api-cpp 1.8.12-1.slc4 glite-security-voms-api-cpp-1.8.12-1.slc4.i386.rpm org.glite.security.voms-api-cpp v. 1.8.12.1
glite-security-voms-clients 1.8.12-1.slc4 glite-security-voms-clients-1.8.12-1.slc4.i386.rpm org.glite.security.voms-clients v. 1.8.12_1
glite-security-voms-config 1.8.12-1.slc4 glite-security-voms-config-1.8.12-1.slc4.i386.rpm org.glite.security.voms-config v. 1.8.12.1
glite-security-voms-oracle 3.1.4-3.slc4 glite-security-voms-oracle-3.1.4-3.slc4.i386.rpm org.glite.security.voms-oracle v. 3.1.4.3
glite-security-voms-server 1.8.12-1.slc4 glite-security-voms-server-1.8.12-1.slc4.i386.rpm org.glite.security.voms-server v. 1.8.12.1

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

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)