Friday, October 16, 2009

Chrome for ETICS

I have tried Chrome with the ETICS web interface and the speed improvement of the JavaScript engine is impressive.

The only catch is the authentication, which you have to solve by command line tools, as Google expects that the OS provides the GUI for certificate handling.

To solve the bootstrapping problem here are some useful commands, given that you have libnss3-tools and ca-policy-igtf-classic installed:


cd ~/.globus
openssl pkcs12 -export -inkey userkey.pem -in usercert.pem -out usercert.p12
certutil -d sql:$HOME/.pki/nssdb -i ~/.globus/usercert.p12
certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n cern-root -i /etc/grid-security/certificates/d254cc30.0
certutil -d sql:$HOME/.pki/nssdb -A -t "C,," -n cern-online -i /etc/grid-security/certificates/1d879c6c.0

Monday, September 14, 2009

GFAL release 1.11.11-1

The release contains the following minor fixes:

- IPv6 compliance
- Manual page update

The release tag is:

glite-data-gfal_R_1_11_11_1

IPv6 compliance in FTS and GFAL

There were several Savannah tasks targeting IPv6 compliance, they have been resolved now. The list of the related tasks:

#41844: IPv6 bug; LCG-utils client functionality immediately broken by IPv6

#41278: IPv6 bug: non compliant address in source code (hard coded IPv4: 127.0.0.1)
#41585: [FTA] IPv6 bug: non compliant name resolving function (gethostbyname_r)
#41586: [FTA] IPv6 bug: non compliant name resolving function in source code (gethostbyname_r)
#41278: IPv6 bug: non compliant address in source code (hard coded IPv4: 127.0.0.1)

See the resolution details in the comments of the individual tasks. Basically, the general solution was:

- remove dependency on the pre-compiled gSoap library
- take stdsoap2.c directly from the gSoap sources
- compile the above file with WITH_IPV6 defined

The release tags including the IPv6 compliance are:

glite-data-srm-api-c_R_1_1_0_12
glite-data-srm2-api-c_R_2_2_0_6
glite-data-transfer-cli_R_3_7_2_1
glite-data-transfer-agents_R_3_4_2_1
glite-data-gfal_R_1_11_11_1

It lists the affected components as well, actually they are the ones that implement SOAP communication with gSoap. The IPv6 functionality is encapsulated into gSoap completely, so we did not have to change the implementation, it was only configuration issue.