Hi,
I have a certificate signing request in the form name.p10 issued by
microsoft outlook which I am trying to sign and issue and certificate for
from my linux server.
I am having some problems finding the correct syntax to treat this type of
file as other requests I have signed have come with
Hello everybody,
I have a question: A client system generates a CSR that contains some
pieces of information and sends the CSR to my CA. What I want to do is
NOT to directly sign the CSR / issue the Certificate but first to
modify or add new pieces of information and then issue the
certificate.
It's not a matter of file name extension. The CA script which comes with
openssl assumes certificate requests are PEM encoded, maybe the request outlook
produced is DER encoded; in that case all you have to do is openssl req -in
your .p10 file -inform der -out a new file name to convert the
A .p10 file *is* the same as a .csr file; the Certificate Signing
Request format is defined in PKCS#10. The only question is whether
the file content begins with an '=' character. If it does, use
-inform PEM; if it doesn't, use -inform DER.
(Considering that it's entirely possible to
Hello everybody,
I have a question: A client system generates a CSR that contains some
pieces of information and sends the CSR to my CA. What I want to do is
NOT to directly sign the CSR / issue the Certificate but first to
modify or add new pieces of information and then issue the
On Tue, Jan 05, 2010, Kyle Hamilton wrote:
A .p10 file *is* the same as a .csr file; the Certificate Signing
Request format is defined in PKCS#10. The only question is whether
the file content begins with an '=' character. If it does, use
-inform PEM; if it doesn't, use -inform DER.
Hi Martin:
On January 5, 2010 02:05:48 pm David Schwartz wrote:
Hello everybody,
I have a question: A client system generates a CSR that contains some
pieces of information and sends the CSR to my CA. What I want to do is
NOT to directly sign the CSR / issue the Certificate but first to
