Thanks for all the replies.
My problem is,
We have one Java based application in which we sign
files using JRE. Now new version of that application
is released. So while upgrading we update only few
files. In the new version we used renewed certificate
(which has OU and L modified)
So while upgr
technically yes, since it must be re-signed and will get a new ID.
max
Josephin wrote:
Hi,
When I'm renewing a certificate, if I'm changing
the OU and L (location), will that certificate will be
treated as a new certificate?
Thanks,
Josephine
_
In message <[EMAIL PROTECTED]> on Tue, 13 Jun 2006 23:27:51 -0700 (PDT),
Josephin <[EMAIL PROTECTED]> said:
j_suganthi> Hi,
j_suganthi>When I'm renewing a certificate, if I'm changing
j_suganthi> the OU and L (location), will that certificate will be
j_suganthi> treated as a new certificate?
Hi,
When I'm renewing a certificate, if I'm changing
the OU and L (location), will that certificate will be
treated as a new certificate?
Thanks,
Josephine
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http:
nagendra <[EMAIL PROTECTED]> writes:
>I've appended the PKCS#7 request generated by IIS to the end of this email.
>IIS creates the header "BEGIN NEW CERTIFICATE REQUEST", which is interpreted
>as an old X509 request (see pem.h).
Ohgodohgod what a mess! That's PKCS #7 signed data containing a da
t;
> > We're generating a CSR on IIS (win2k). When a certificate is already
> > installed on IIS, it generates a PKCS#7 certificate renewal request rather
> > than a PKCS#10 CSR. Furthermore the PEM header in the request is an
> > invalid PKCS#7 header. As a result no
nagendra wrote:
>
> Hi,
>
> We're generating a CSR on IIS (win2k). When a certificate is already
> installed on IIS, it generates a PKCS#7 certificate renewal request rather
> than a PKCS#10 CSR. Furthermore the PEM header in the request is an
> invalid PKCS#7 heade
Hi,
We're generating a CSR on IIS (win2k). When a certificate is already
installed on IIS, it generates a PKCS#7 certificate renewal request rather
than a PKCS#10 CSR. Furthermore the PEM header in the request is an
invalid PKCS#7 header. As a result none of the openssl utilities can pars
