It's actually being fixed in VDT 1.10.1, which will be released early
next week.
I've never seen the error in VDT 1.8.x, so if it's there, I definitely
want to see it. Please send me the file created by running "vdt-system-
profiler".
-alain
On May 9, 2008, at 9:24 AM, Charles Bacon wrote:
It is, but I believe you have to be up at VDT 1.10.0 before you get
GT4.0.7. VDT 1.8.0 is based on GT4.0.5, which would not exhibit
these errors. Are you sure this isn't VDT 1.10.0? If it is, then
Alain is already building an update that contains the advisories Tom
mentions.
So, if it's really VDT 1.8.0, then there's some serious
investigation to be done. If it's VDT 1.10, you can either wait for
the VDT update, or apply the GT advisories to solve it immediately.
Charles
On May 9, 2008, at 7:27 AM, Tom Scavo wrote:
On Fri, May 9, 2008 at 12:16 AM, Andrey Kharuk <[EMAIL PROTECTED]
> wrote:
We just installed VDT 1.8. One of the troubles is a plenty records
in
container-real.log file with two kinds of errors (see below).
First kind of
errors relates to all certificates where in *.signing_policy files
DNs are
used without double quotes inside single quotes. I mean if DN
looks like
'"/C=US/O=SDSC/*"' then a certificate could be loaded.
An advisory was posted related to GT 4.0.7 and signing policy files:
http://www.globus.org/toolkit/advisories.html
Could it be that VDT 1.8 is based on GT 4.0.7?
Tom
