gLite 3.1
glite-VOBOX - Update to version 3.1.21-0
|
Date |
16.12.2008 |
Priority |
Normal |
Description
The following fixes are released with glite-VOBOX 3.1.21-0:
1. New features for the hydra clients have been included:
- split-key support using Shamir's Secret Sharing Scheme
- using GFAL for I/O (replacing gLite I/O)
Known bugs:
- glite-eds-put doesn't work as documented. It cannot use lfc's GUID:s, so "-i keyname" must be specified on the command line
2. Upgrade of lcg-vomscerts-5.2.0:
- renamed all certificates with ".pem" suffixes because of bug 43395.
- removed expired certificate of voms.cern.ch
3. 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 VOBOX is working, this change has no effect. When the VOBOX 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.
4. 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 |
#12669 |
EDS client should make use of multiple keystores |
#31583 |
glite-eds-key-register may unregister valid entities on 'exist' error |
#40190 |
File (-MDX) operations not working with glite-eds-setacl |
#41592 |
glite-eds-put doesn't work without specifying a key |
#43395 |
Request to have voms cert file called <something>.pem |
#45278 |
Removing Multivalue SE from GlueCESEBind |
Updated rpms
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
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|