Note: This version of the VDT (1.8.1) is no longer supported. Feel free to look through the documentation and install it, but we cannot guarantee support for it. The current stable release is 2.0.0.

VDT 1.8.1e Update

On 2007-11-21, the VDT team announced the release of VDT 1.8.1e.

Changes to VDT 1.8.1e

VOMS Admin (the web front-end to VOMS) has been updated to version 1.2.19-3. This release fixes a security vulnerability. Details about this security vulnerability will be forthcoming soon.
glexec was updated to deal with a potential security issue. (VDT ticket 3126)
The vdt-update-certs script in CA-Certificates-Updater has been updated to prevent an issue with clients synchronizing after a long outage of the VDT web server. (VDT ticket 2916)
SLES-9 x86_64 is now supported. The majority of the VDT has been validated on this platform. One notable exception is that PRIMA is currently unsupported. Additionally, 32-on-x86_64 installs are not supported. Please let us know if you have any problems on this platform.

Updating to VDT 1.8.1e

If you installed VDT 1.8.1 after VDT 1.8.1e was released on 2007-11-21, you do not need to do any of these update operations because you will have 1.8.1e.

The best way to do the update is to update the individual packages that have changed. To be clear, we do not recommend using pacman -update without specifying specific package names. Also note that you only need to update packages if you installed them. You can see what packages have been installed with:

pacman -l -d 1

Common update directions

Before you do the update directions that follow, please run the following commands. They apply for all of the updates.

cp -pr $VDT_LOCATION BACKUP-LOCATION
cd $VDT_LOCATION
. setup.sh

The copy command makes a complete backup of your VDT installation, in case something goes wrong. Do not skip this step!

1. Updating VOMS Admin

pacman -update VOMS-Admin

2. Updating Glexec

pacman -update Glexec

3. Updating CA-Certificates-Updater

pacman -update CA-Certificates-Updater