[AG-TECH] Problems getting started with AG2.1

[Robert Olson]

For those who aren't paying close attention, the following is a fix for a 
problem involving trusted CA certificates whose filenames begin with 0.

At 05:23 PM 10/22/2003 +0100, pns at soc.soton.ac.uk wrote:
>As I mentioned, the signing policy was absent from
>../AccessGrid/trustedCACerts, so I copied it over again.
>On starting up the venue client, I got the same problem as before.
>When I looked at the files in the trustedCACerts dir,  I find that the
>01621954_signing_policy file has disappeared, and the CA cert filename has
>now lost it's leading zero to become 1621954.0

The problem here is in pyOpenSSL, one of the packages that supports the 
AGTk certificate management code. I've placed a fixed pyOpenSSL installer at

http://www-unix.mcs.anl.gov/fl/research/accessgrid/software/releases/2.1.2/windows/pyOpenSSL-2003-1022.exe

(aka http://snurl.com/elh for now anyway).

The MD5 checksum:

32ae04b8244759d9a14a6216ab157f91  pyOpenSSL-2003-1022.exe

To install this, first ensure that your venue client is not running (the 
install will fail due to files being in use).

Download the aforementioned file and execute it. It'll prompt for a python 
version, which in most cases should be correct. Answer "Yes" to the 
question about overwriting files. When it completes, start your venue 
client again. It will regenerate the trusted CA certs directory with the 
proper filenames. Mine now looks something like this:

10/22/2003  01:40 PM    <DIR>          ..
10/22/2003  01:40 PM             1,786 01621954.0
10/22/2003  01:40 PM               626 01621954.signing_policy
10/22/2003  01:40 PM               820 42864e48.0
10/22/2003  01:40 PM             1,362 42864e48.signing_policy
10/22/2003  01:40 PM               920 45cc9e80.0
10/22/2003  01:40 PM             1,367 45cc9e80.signing_policy
                6 File(s)          6,881 bytes

Please let me know if you have any questions or problems with this.