gLite 3.1
glite-WN - Update to version 3.1.11-0
|
Date |
16.12.2008 |
Priority |
Normal |
Description
Major features in glite-data-hydra-service v1.3.0-1 and
glite-data-hydra-cli v3.1.0-1:
o split-key support using Shamir's Secret Sharing Scheme
o using GFAL for I/O (replacing gLite I/O)
Known bugs:
o 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
lcg-vomscerts-5.2.0:
- renamed all certificates with ".pem" suffixes because of bug 43395
- removed expired certificate of voms.cern.ch
This is a simple fix for the library moving problem.
If the service is working, this change has no effect. When the service is next time reconfigured or if there is a clean install this change has an effect and will use the algorithm described in the original submission comment.
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.
This is a simple fix for the library moving problem.
If the service is working, this change has no effect. When the service is next time reconfigured or if there is a clean install this change has an effect and will use the algorithm described in the original submission comment.
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. That's why it's better to reconfigure the services that run on tomcat.
But the WN doesn't have services running on tomcat, thus this is just a synchronization update to be in sync with other components
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 |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Not needed.
Service restart after update
Not needed.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|