ok, the expiry date was in the pass!!!!!!
matt did a edg-fetch-crl and now all is well ( with this aspect anyway!!!)
thanks
brian
On 25/08/05, Jensen, J (Jens) <[log in to unmask]> wrote:
> brian davies sent on 25 August 2005 16:57
> >
> >
> > hi
> > from my ui I can grid-proxy-init and voms-proxy-init.
> > however if i then try to myproxy-init -d i get a failure in that it
> > can not verify the user credential to generate a proxy from
> > ( and then states thar grid-proxy-init failed)
> > is this a crl problem?
> > noticed that new certs are 1024 bits where as my current is only
> > 512bits, does this matter?
> > brian
> >
>
> Brian,
>
> Not sure what the problem is but a few points:
>
> myproxy-init does not use the proxy generated with
> {grid,voms}-proxy-init or with myproxy-get-delegation.
> {grid,voms}-proxy-init and myproxy-init all use your certificate and
> private key.
>
> This is confusing because most other myproxy-* commands _do_ use the
> proxy.
>
> You can check the CRL with
> openssl crl -in /etc/grid-security/certificates/01621954.r0 -noout -nextupdate
>
> It will display the date when the CRL "expires". It should be in
> the future.
>
> Also, proxy certificates have 512 bit keys and user certificates have
> 1024 bit keys (or 2048). But in general the key size shouldn't matter
> (although in practice, sometimes it does).
>
> And finally, I just tried on RAL's UI what you just did and it worked.
> Does the above help you narrow down the problem?
>
> --jens
>
