I generated a cert for your privatekey using a fake CA I have
for my testing (which I already set up in my systems).
If you want to set up your own, it's simple in principle, but
there are quite a few options and details. At a minimum:
- create a CA key and a selfsigned (root) cert for
Thank you very much.
Sent from Surface Pro
From: Dave Thompson
Sent: Tuesday, March 25, 2014 1:58 AM
To: openssl-users@openssl.org
I generated a cert for your privatekey using a fake CA I have
for my testing (which I already set up in my systems).
If you want to
Dear Dave,
thanks, I modified the program and it works.
I got another question:
I compare the two files, one made by the program with the C API, and the
other made by command line tool.
There is one difference: after the sha1 line there is a NULL. I can't
reproduce it with the C API.
C src:
On Fri, Mar 21, 2014 at 12:25 AM, Stefan H. Holek ste...@epy.co.at wrote:
I have updated the OpenSSL PKI Tutorial at Read the Docs. The tutorial
provides three complete PKI examples you can play through and the prettiest
configuration files this side of Neptune. Check it out!
Le 25/03/2014 17:44, Zack Williams a écrit :
On Fri, Mar 21, 2014 at 12:25 AM, Stefan H. Holek ste...@epy.co.at wrote:
I have updated the OpenSSL PKI Tutorial at Read the Docs. The tutorial provides
three complete PKI examples you can play through and the prettiest
configuration files this
The parameters field in an AlgorithmIdentifier is optional if NULL,
which it is for SHA-1, and SHA-2 and I think all hashes as well as many
other algorithms. It appears the (older) SMIME_ API and smime utility
does encode it and the (newer) CMS_ API and cms utility does not.
A compliant
On Tue, Mar 25, 2014 at 10:54 AM, Erwann Abalea
erwann.aba...@keynectis.com wrote:
2. I couldn't figure out what the [additional_oids] section of the
Expert example's root-ca.conf file is for - either through research or
going through the commit history. Could you elaborate on what that
