gLite 3.1
glite-GLEXEC_wn - Update to version 3.1.2-0
|
| Date |
31.08.2009 |
| Priority |
Normal |
Description
glite-GLEXEC_wn
New glexec wrapper scripts
All the detailed information about these scripts is here.
Background information: The gLExec wrapper scripts are able to preserve the process environment variable in a safe way.
As a security measure gLExec will wipe all environment variables from the process to avoid tampering or exploitation.
This has been a struggle for Pilot Job Framework (PJF) developers to be able to overcome this security measure. Each PJF
would have to come up with their own solutions to be able to preserve the environment variables which are used a a form
of global variable space, paths to specific software areas, or other unknown use cases.To help the VOs we've come up with
these scripts to have a easy to use, uniform and supported way of preserving the environment variable between the users contexts in a safe way.
lcg-CE, glite-WMS, glite-SCAS, glite-GLEXEC_wn, glite-CREAM, glite-VOBOX
New version of lcas and lcas interface
This is a drop-in replacement for lcas and lcas-interface. It was triggered by a faulty globus call which has been replaced by local code.
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 |
|
#23534 |
Problem with lcas-voms-plugin in glexec |
|
#29845 |
LCAS fails to parse "multi-delegated" proxy |
|
#41472 |
glexec fails if valid VOMS proxy also contains expired extensions |
|
#43842 |
LCAS seg faults on wrong certificate selection in certain cases |
|
#46037 |
When using glexec on a WN, the LCAS userban plugin has a malformed user DN |
|
#47661 |
Error messages in log file when glexec fails because proxy is expired |
|
#51854 |
gLExec environment to be passed in safe mode to payload shell |
|
#52054 |
[LCAS/VOMS-API] Segfault when number of proxy delegations > number of RDn's |
|
#52417 |
[LCAS] lcas segfaults when proxy is malformed |
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)
|
|
