<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
Hi, <br>
<br>
Dean and Rachana are on the case.<br>
I am sure when they have something they'll let us know.<br>
<br>
As it stands right now... the script generates the CSR that you can
submit to get signed. If you already have a keypair you can use
that and call esg-node --install-keypair and it will do the right
things. So who you use to sign your CSR is up to you... and as I
mentioned if you already have a keypair you can directly use it.
:-). Everyone is free to do as they wish. :-)<br>
[note: you have to have all the certs in the cert chain if your CA's
cert is in a chain]<br>
<br>
There is no single point of failure in this scenario. The only
thing that matters is that you have your CA's public cert in your
truststore and /etc/grid-security. You don't need to communicate to
the CA at all, you just need them to sign an provide you their
cert. Done.<br>
<br>
Essentially we would be establishing membership (those that can be
authenticated thus trusted to talk to) in a peer2peer mesh network
by the CA that vouches for that network. There should only be one
per mesh. In our case that "one" is ESGF but there is no barrier to
having a peer support one or many CAs... well, except if you want
your clients to use Safari ;-).<br>
<br>
Another note about the installer... the installer under
--install-keypair will take the keypair you give it and convert and
insert it into your keystore as well as /etc/grid-security... It is
the same cert in two formats. Thus the entire node is represented
by one DN that is used for gridftp and tomcat. The idea there is to
minimize the amount of certs you have to manage. Don't confuse this
with the ability to recognize and validate against all the certs you
encounter by putting them in the truststore and
/etc/grid-security/certs.<br>
<br>
P.S.<br>
Pardon, yes I did mean Estani and everyone on the list, etc... :-)
and you.<br>
<br>
On 6/1/11 4:28 PM, Cinquini, Luca (3880) wrote:
<blockquote
cite="mid:957190B3-F034-4DC0-8ADA-7821E33C51ED@jpl.nasa.gov"
type="cite">Hi Gavin,
<div><span class="Apple-tab-span" style="white-space: pre;"> </span>I
think you meant "Estani"...</div>
<div>Anyway, I like the idea of a single ESGF CA. Can we make it
happen ? Maybe at installation time you can be given the option
of generating your own cert (so that we don't completely make
ourselves depending on a single point of failure), or have it
signed by another CA. What would be the best location for such a
CA - PCMDI or ANL perhaps ?</div>
<div>thanks, Luca</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Gavin M. Bell
Lawrence Livermore National Labs
--
"Never mistake a clear view for a short distance."
-Paul Saffo
(GPG Key - <a class="moz-txt-link-freetext" href="http://rainbow.llnl.gov/dist/keys/gavin.asc">http://rainbow.llnl.gov/dist/keys/gavin.asc</a>)
A796 CE39 9C31 68A4 52A7 1F6B 66B7 B250 21D5 6D3E
</pre>
</body>
</html>