Automatically generated by Pod::Man 4.07 (Pod::Simple 3.32) Standard preamble: ========================================================================
NAMECA.pl - friendlier interface for OpenSSL certificate programs
- ?, -h, -help
- prints a usage message.
- creates a new self signed certificate. The private key is written to the file ``newkey.pem'' and the request written to the file ``newreq.pem''.
- creates a new certificate request. The private key is written to the file ``newkey.pem'' and the request written to the file ``newreq.pem''.
- is like -newreq except that the private key will not be encrypted.
creates a new CAhierarchy for use with the ca program (or the -signcert and -xsign options). The user is prompted to enter the filename of theCAcertificates (which should also contain the private key) or by hittingENTERdetails of theCAwill be prompted for. The relevant files and directories are created in a directory called ``demoCA'' in the current directory.
create a PKCS#12 file containing the user certificate, private key and CAcertificate. It expects the user certificate and private key to be in the file ``newcert.pem'' and theCAcertificate to be in the file demoCA/cacert.pem, it creates a file ``newcert.p12''. This command can thus be called after the -sign option. The PKCS#12 file can be imported directly into a browser. If there is an additional argument on the command line it will be used as the ``friendly name'' for the certificate (which is typically displayed in the browser list box), otherwise the name ``My Certificate'' is used.
- -sign, -signreq, -xsign
- calls the ca program to sign a certificate request. It expects the request to be in the file ``newreq.pem''. The new certificate is written to the file ``newcert.pem'' except in the case of the -xsign option when it is written to standard output.
this option is the same as the -signreq option except it uses the configuration
file section v3_ca and so makes the signed request a valid CAcertificate. This is useful when creating intermediateCAfrom a rootCA.
- this option is the same as -sign except it expects a self signed certificate to be present in the file ``newreq.pem''.
verifies certificates against the CAcertificate for ``demoCA''. If no certificates are specified on the command line it tries to verify the file ``newcert.pem''.
- one or more optional certificate file names for use with the -verify command.
Complete certificate creation example: create a
CA.pl -newca CA.pl -newreq CA.pl -signreq CA.pl -pkcs12 "My Test Certificate"
DSA CERTIFICATESAlthough the
openssl dsaparam -out dsap.pem 1024
openssl req -x509 -newkey dsa:dsap.pem -keyout cacert.pem -out cacert.pem
enter cacert.pem when prompted for the
openssl req -out newreq.pem -newkey dsa:dsap.pem
Sign the request:
NOTESMost of the filenames mentioned can be modified by editing the
If the demoCA directory already exists then the -newca command will not overwrite it and will do nothing. This can happen if a previous call using the -newca option terminated abnormally. To get the correct behaviour delete the demoCA directory if it already exists.
Under some environments it may not be possible to run the
perl -S CA.pl
can be used and the
The script is intended as a simple front end for the openssl program for use by a beginner. Its behaviour isn't always what is wanted. For more control over the behaviour of the certificate commands call the openssl command directly.