[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
v2.2.1 Certificate Management Library (CML) Now Available
All,
DigitalNet has delivered the Version 2.2.1 Certificate Management
Library (CML) for Microsoft Windows, Sun Solaris, and Linux. The
v2.2.1 CML and documentation is freely available at:
<http://www.digitalnet.com/hot/cml_home.htm>.
Applications requiring Public Key Infrastructure (PKI) security
services can use the CML to meet their X.509 certificate and
Certificate Revocation List (CRL) processing requirements.
The v2.2.1 CML is described in the v2.2.1 CML Application Programming
Interface (API) document. It implements the 2000 X.509 Recommendation
certification path verification processing rules and SDN.706 profile.
It meets the majority of the IETF PKIX RFC 3280 Certificate/CRL Profile
requirements. There are some unsupported features such as
Delta CRLs. The v2.2.1 CML Abstract Syntax Notation One (ASN.1)
decodes X.509 Certificates and CRLs. It requires the v1.5.1
Enhanced SNACC ASN.1 software that is freely available from:
<http://www.digitalnet.com/hot/snacc_home.htm>.
The CML provides robust certification path building capabilities such
as using cross certificates. The CML uses the accompanying Storage
and Retrieval Library (SRL) (optionally) to provide local certificate
and CRL storage management functions. The SRL (optionally) provides
remote directory retrieval capabilities using the Lightweight
Directory Access Protocol (LDAP).
The CML has been thoroughly tested including validating X.509
Certificates and CRLs created by a variety of Certification
Authority (CA) products, and signed using the Digital Signature
Algorithm (DSA) and RSA algorithms. Further enhancements,
ports and testing of the CML are still in process. Further
releases of the CML will be provided as significant
capabilities are added.
v2.2.1 CML includes the following enhancements (compared to v2.2
CML release):
1) Added --enable-onlycml to configure. This builds the Makefiles so
that only the cml and related libraries are built.
2) Modified how threads were determined during configure.
3) Modified the check for the ldap library, it now checks to see if
there is a liblber.so library
4) If BSAFE was on the system, but user did not want to use it, the user
had no choice but use it, this is now optional.
5) Added check for SunOS when ldap libraries are present.
6) Modified the configure environment to use the file Makehead for
global make variables and settings. Configure will create this file.
7) CML v2.2.1 was successfully tested on HP-UX 11, SCO System 5, and
Microsoft Visual Studio 7 (.Net).
8) Please see the CML Readme file for further information regarding bug
fixes.
v2.2.1 SRL includes the following enhancements (compared to v2.2
SRL release):
1) Fixed thread problem in SRLi_LdapConnect(), that caused the function
to exception on some instances causing unknown exceptions.
2) Fixed resource leak on the db mutex.
All source code for the CML is being provided at no cost and with no
financial limitations regarding its use and distribution. Organizations
can use the CML without paying any royalties or licensing fees. The
CML was originally developed by the U.S. Government. DigitalNet is
enhancing and supporting the CML under contract to the U.S. Government.
The U.S. Government is furnishing the CML software at no cost to the
vendor subject to the conditions of the CML Public License provided
with the CML software.
The CML makes calls to an algorithm-independent CTIL API that provides
access to a variety of external crypto libraries. There is a CTIL for
each crypto library that maps the generic CTIL API calls to the
specific calls for that crypto library. DigitalNet provides CTILs for
the Microsoft CAPI v2.0, Crypto++, RSA BSAFE, Spyrus SPEX/ and
FORTEZZA Cryptologic Interface libraries. DigitalNet also provides a
PKCS #11 CTIL that enables PKCS #11-compliant libraries to be used
with the CML. The underlying, external crypto libraries are not
distributed as part of the CML software.
The CML has been successfully tested with the v2.2 S/MIME Freeware
Library (SFL) that is freely available from
<http://www.DigitalNet.com/hot/sfl_home.htm>.
The CML has been successfully tested with the v2.2 Access Control
Library (ACL) that is freely available to everyone from:
<http://www.DigitalNet.com/hot/acl_home.htm>.
The CML has been successfully used to build and verify
certificate paths used in the Bridge Certification Authority (BCA)
demonstration which includes cross-certified hierarchical and non-
hierarchical PKIs. The BCA Interoperability Test Suite (BITS)
is a free and openly available test resource provided to
facilitate vendor development of secure, interoperable Public
Key Enabled applications. The CML has been used to successfully
develop and verify the BITS X.509 certification paths available
from <http://bcatest.atl.DigitalNet.com>.
The National Institute of Standards and Technology (NIST) is
providing a standard test suite of X.509 certificate paths
<http://csrc.nist.gov/pki/testing/x509paths.html> that can be
used for testing applications against RFC 2459. The CML was
used to successfully process the NIST test data.
The CML meets the requirements stated in the SDN.706 Certificate/
CRL Profile required by the U.S. Defense Message System (DMS)
project.
The Internet Mail Consortium (IMC) has established a CML web page
<http://www.imc.org/imc-cml> and a CML mail list which is used to:
distribute information regarding CML releases; discuss CML-related
issues; and allow CML users to provide feedback, comments, bug
reports, etc. Subscription information for the imc-cml mailing list
is at the IMC web site listed above.
All comments regarding the CML source code and documents are welcome.
This CML release announcement was sent to several mail lists, but
please send all messages regarding the CML to the imc-cml mail list
ONLY. Please do not send messages regarding the CML to any of the IETF
mail lists. We will respond to all messages sent to the imc-cml mail
list.
--
Matthew J. Bertapelle
DigitalNet Government Solutions, LLC.
Matt.Bertapelle@xxxxxxxxxxxxxx