Jim
that completely resolved my problem.
Thank you
saludos,
José Luis Gordillo Ruiz
Coordinación de Supercómputo
UNAM
El 30/07/2014, a las 20:21, Basney, Jim jbas...@illinois.edu escribió:
Hi José,
My guess is that you want to set the GLOBUS_HOSTNAME environment variable [1
N=nodoa.super.unam.mx>
New trusted CA (d3b04078.0):
/O=Grid/OU=GlobusTest/OU=simpleCA-nodoa.super.unam.mx/CN=Globus
<http://simpleca-nodoa.super.unam.mx/CN=Globus> Simple CA
I’ve tryed in several clients and the result is the same
Any ideas?
thank you in advance
saludos,
José Luis Go
Jim, Mike,
thank you for your help. Effectively, using globes-update-certificate-dir with
-subject_hash_old solve
the hashes issue, and also I’m now able to use clients from Mac OS El Capitan.
saludos,
José Luis Gordillo Ruiz Coordinación de Supercómputo - DGTIC
On mar, ene 26, 2016 at 7:59 p.m
MacOS but I can from Linux (with same user certificate, same servers, etc).
I’ve been tracking down differences bt the clients and I found this difference
in setting trust roots.
saludos,
José Luis Gordillo Ruiz Coordinación de Supercómputo - DGTIC
Hi all,
I recently got into a similar problem. It’s a hostname resolution issue.
see the thread for
https://lists.globus.org/mailman/htdig/gt-user/2007-May/003429.html
<https://lists.globus.org/mailman/htdig/gt-user/2007-May/003429.html>
saludos,
José Luis Gordillo Ruiz
Coordinac