EJBCA, J2EE PKI Certificate Authority: 3.8.1 released
EJBCA is an enterprise class PKI Certificate Authority built on J2EE technology. It is a robust, high performance, platform independent, flexible, and component based CA to be used standalone or integrated in other J2EE applications.
:rolleyes:I am trying to setup all certificate based client-server environment in Linux using vsftpd and curl with openssl.
I would like to make a user access with vsftpd certificate and user own client certificate (self-signed) with private/public key.
I don't see google posts about the my plan... (4 Replies)
Hi guys,
I'm going to start studding about J2EE in a couple of weeks. I have no idea about its technologies. what prerequisites do i need. I only know java and have basic knowledge about HTML. I have a solid knowledge on database.
1. Do i need java script or CSS knowledge for JSP and JSF?
2.... (1 Reply)
I am looking for someone who has implemented CAC/PKI authentication on Apache 2.2.x and Solaris 10. Not Linux. I need to compare notes and my plan of attack. (0 Replies)
Hi, I'm tryng to install the J2EE 1.4 on Solaris 8, but I'm getting an error message, saying I don't have enough space on the device....but I DO have...heres a df -k:
I'm trying to install in /export/home.......
Help?? (12 Replies)
PKI --REQ(1) strongSwan PKI --REQ(1)NAME
pki --req - Create a PKCS#10 certificate request
SYNOPSIS
pki --req [--in file] [--type type] --dn distinguished-name [--san subjectAltName] [--password password] [--digest digest]
[--outform encoding] [--debug level]
pki --req --options file
pki --req -h | --help
DESCRIPTION
This sub-command of pki(1) is used to create a PKCS#10 certificate request.
OPTIONS -h, --help
Print usage information with a summary of the available options.
-v, --debug level
Set debug level, default: 1.
-+, --options file
Read command line options from file.
-i, --in file
Private key input file. If not given the key is read from STDIN.
-t, --type type
Type of the input key. Either rsa or ecdsa, defaults to rsa.
-d, --dn distinguished-name
Subject distinguished name (DN). Required.
-a, --san subjectAltName
subjectAltName extension to include in request. Can be used multiple times.
-p, --password password
The challengePassword to include in the certificate request.
-g, --digest digest
Digest to use for signature creation. One of md5, sha1, sha224, sha256, sha384, or sha512. Defaults to sha1.
-f, --outform encoding
Encoding of the created certificate file. Either der (ASN.1 DER) or pem (Base64 PEM), defaults to der.
EXAMPLES
Generate a certificate request for an RSA key, with a subjectAltName extension:
pki --req --in key.der --dn "C=CH, O=strongSwan, CN=moon"
--san moon@strongswan.org > req.der
Generate a certificate request for an ECDSA key and a different digest:
pki --req --in key.der --type ecdsa --digest sha256
--dn "C=CH, O=strongSwan, CN=carol" > req.der
SEE ALSO pki(1)5.1.1 2013-07-31 PKI --REQ(1)