Free ca software for linux

This application is a graphical user interface to OpenSSL, RSA public keys, certificates, signing requests and revokation lists.
The keys do have an internal counter, counting its use to avoid a duplicate use of a key for creating a certificate or request. The Keys are encrypted in the database file.
Xca supports next to the usual PEM and DER format of certificates the import and export of PKCS#12 (aka *.pfx) files and the Certificate import from PKCS#7 files.
Certificates can be created by self signing it, by signing it by an other (usually CA) certificate or by signing a PKCS#10 request. Netscape SPKAC is supported since version 0.4.6. The validity dates and x509.v3 extensions can be adjusted to fit ones needs. The use of multiple certificates in CA chains is supported and a tree view of the certificates reflects the dependencies. The application takes care to not create duplicate certificates by checking the serial number(s) on import and creation of certificates.
Certificate Templates can be used to preset the input dialog with reasonable values and to simplify the process of creating certificates and requests.
Issued certificates can be revoked and the revokation list can be created and exported. External revokation lists can be imported and examined.
Main features:
- Database
- Uses one local databasefile for all settings, Keys, Requests and Certificates. IMHO it is an advantage and not a disadvantage
- transactions, recovery and db-exceptions are used to keep it consistent.
- Keys
- import and export of PEM, DER, PKCS#8 private and public RSA keys.
- Key generation with variable length
- Keys are 3-DES encrypted in database
- PKCS#10 Requests
- import and export of Requests.
- Request generation.
- X509 Certificates
- Generation of self signed and foreign signed Certificates.
- Tree view of Certificate chains.
- All x509 v3 extensions are implemented.
- Certificate dependend autoincrementing serialnumbers.
- Pre setting of the signing serial number.
- Shows Subject, Issuer, Serial, Dates, V3 extensions, SHA1 and MD5 fingerprints.
- CRL export for CA certificates.
- generate request from certificate.
- import and export in DER, PEM and PKCS#12 format.
- several export formats containing certificate chains or not.
- Signing and encryption of files added, they are written in PEM PKCS#7 format
- Export to TinyCA or "openssl ca" filestructure
- Certificates in tree view or in plain view
- Sorting of certificates by date or serial
- All known X.509 name-entry OIDs can be used in the distinguished name
- The hash algorithm for signing is selectable
- templates
- Generation of predefined CA, Client and Server Templates.
- Certificates and Requests can use the Templates
- Revokation lists
- Import, export, detailed view and creation of CRLs
Enhancements:
- Break endless loop in chain building. Bug [ 1696878 ]

TinyCA is a simple graphical userinterface written in Gtk/Perl to manage a small CA (Certification Authority).
TinyCA works as a frontend for openssl.
Main features:
- Unlimited CAs possible
- Support for creating and managimg SubCAs
- Creation and Revocation of x509 - S/MIME certificates
- PKCS#10 Requests can be imported and signed
- RSA and DSA keys can be generated and used
- ServerCertificates
- Certificates can be exported as: PEM, DER, TXT and PKCS#12
- Certificates may be used with e.g. Apache, Postfix, OpenLDAP, Cyrus and FreeS/WAN
- ClientCertificates
- Certificates can be exported as: PEM, DER, TXT and PKCS#12
- Certificates may be used with e.g. Netscape, Konqueror, Opera, Internet Explorer, Outlook (Express) and FreeS/WAN
- Certificate Revocation List
- CRLs can be exported as: PEM, DER and TXT
Language Support:
- English
- German
- Spanish
- Czech
- French

CA::AutoSys is a Perl interface to CAs AutoSys job control.

SYNOPSIS

use CA::AutoSys;

my $hdl = CA::AutoSys->new( [OPT] ) ;
my $jobs = $hdl->find_jobs($jobname) ;
while (my $job = $jobs->next_job()) {
:
}
my $status = $job->get_status() ;
my $children = $job->find_children() ;
while (my $child = $children->next_child()) {
:
}

CLASS METHODS

new()
my $hdl = CA::AutoSys->new( [OPT] ) ;

Creates a new CA::AutoSys object.

Below is a list of valid options:

dsn

Specify the DSN of the AutoSys database server to connect to. If nothing is specified, Sybase will be assumed: dbi:Sybase:server= With this option you should be able to connect to databases other than Sybase.

server

Specify the AutoSys database server to connect to. Either this option or the dsn option above must be given. Please note, that when specifying this server option, a Sybase database backend is assumed.

user

Specify the database user. With an out-of-the-box AutoSys installation, the default user should work.

password

Specify the database password. With an out-of-the-box AutoSys installation, the default password should work.

Example:

my $hdl = CA::AutoSys->new(server => "AUTOSYS_DEV");

Ca$h or Cra$h project is a computerized clone of the US version of the "Deal or No Deal" game show. The game consist of selecting one of twenty-six cases, each with a random amount of money inside at preselected values ranging from a penny to $1 million.

Then each of the other twenty-five cases are opened, one at a time, knocking off values. Every so often, the banker will offer you an amount of money for your case. The game ends when you either make a deal for your case or you open one of two remaining cases.

Crypt::OpenSSL::CA::Resources is a bibliography of documentations and tools that I found helpful for implementing X509 PKIs in Perl over all these years.

This package performs the cryptographic operations necessary to issue X509 certificates and certificate revocation lists (CRLs). It is implemented as a Perl wrapper around the popular OpenSSL library. All certificate and CRL extensions supported by OpenSSL are available, and then some.

Odyssi Certificate Server is a Java-based certificate authority server.
Odyssi Certificate Authority Server is released as 100% free software under the GNU General Public License (GPL). You are free to make changes to any of its components for deployment within your own organization. This provides you the freedom to integrate the CA with your existing systems and resources.
In addition, Odyssi CA makes use of other award-winning Open Source products, such as Hibernate, Apache Tomcat, Apache Axis, and others. Open Source database products, such as MySQL and PostgreSQL, are also fully-supported, allowing you to run your entire CA infrastructure on an Open Source platform. And, because Odyssi CA is written completely in Java, it will work on any platform with a Java VM.
Enhancements:
- This release provides minimal support for submitting certificate requests and generating X.509 certificates.

Graphical certification authority project is a graphical user interface to OpenSSL, RSA/DSA public keys, certificates, signing requests and revokation lists.
The keys have an internal counter, counting its use to avoid a duplicate use of a key for creating a certificate or request.
The Keys are of course encrypted in the db file.
Xca supports next to the usual PEM and DER format of certificates the import and export of PKCS#12 (aka *.pfx) files and the Certificate import from PKCS#7 files.
Certificates can be created by self signing it, by signing it by an other (usually CA) certificate or by signing a PKCS#10 request. Netscape SPKAC is supported since version 0.4.6. The validity dates and x509.v3 extensions can be adjusted to fit ones needs. The use of multiple certificates in CA chains is supported and a tree view of the certificates reflects the dependencies. The application takes care to not create duplicate certificates by checking the serial number(s) on import and creation of certificates.
Certificate Templates can be used to preset the input dialog with reasonable values and to simplify the process of creating certificates and requests.
Issued certificates can be revoked and the revokation list can be created and exported. External revokation lists can be imported and examined.
Enhancements:
- This version fixes an issue where some CA signed certificates were not sorted correctly below that CA.
- Malformed certificates no longer cause a crash.
- The string encoding rules for the distinguished name can now be set in the options dialog and PKCS#10 attributes can be set and inspected.

Crypt::SSLeay is a Perl module for OpenSSL glue that provides LWP https support.

SYNOPSIS

lwp-request https://www.nodeworks.com

use LWP::UserAgent;
my $ua = new LWP::UserAgent;
my $req = new HTTP::Request(GET, https://www.nodeworks.com);
my $res = $ua->request($req);
print $res->code."n";

# PROXY SUPPORT
$ENV{HTTPS_PROXY} = http://proxy_hostname_or_ip:port;

# PROXY_BASIC_AUTH
$ENV{HTTPS_PROXY_USERNAME} = username;
$ENV{HTTPS_PROXY_PASSWORD} = password;

# DEBUGGING SWITCH / LOW LEVEL SSL DIAGNOSTICS
$ENV{HTTPS_DEBUG} = 1;

# DEFAULT SSL VERSION
$ENV{HTTPS_VERSION} = 3;

# CLIENT CERT SUPPORT
$ENV{HTTPS_CERT_FILE} = certs/notacacert.pem;
$ENV{HTTPS_KEY_FILE} = certs/notacakeynopass.pem;

# CA CERT PEER VERIFICATION
$ENV{HTTPS_CA_FILE} = certs/ca-bundle.crt;
$ENV{HTTPS_CA_DIR} = certs/;

# CLIENT PKCS12 CERT SUPPORT
$ENV{HTTPS_PKCS12_FILE} = certs/pkcs12.pkcs12;
$ENV{HTTPS_PKCS12_PASSWORD} = PKCS12_PASSWORD;

This perl module provides support for the https protocol under LWP, so that a LWP::UserAgent can make https GET & HEAD & POST requests. Please see perldoc LWP for more information on POST requests.

The Crypt::SSLeay package contains Net::SSL, which is automatically loaded by LWP::Protocol::https on https requests, and provides the necessary SSL glue for that module to work via these deprecated modules:

Crypt::SSLeay::CTX
Crypt::SSLeay::Conn
Crypt::SSLeay::X509

Work on Crypt::SSLeay has been continued only to provide https support for the LWP - libwww perl libraries. If you want access to the OpenSSL API via perl, check out Sampos Net::SSLeay.