Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

Legion of the Bouncy Castle Java Cryptography API 1.39 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Legion of the Bouncy Castle Java Cryptography API 1.39 (Default branch)
# 1  
Old 03-31-2008
Legion of the Bouncy Castle Java Cryptography API 1.39 (Default branch)
The Legion of the Bouncy Castle Java CryptographyAPI provides a lightweight cryptography API inJava, a provider for the JCE and JCA, a clean-roomimplementation of the JCE 1.2.1, generators forVersion 1 and Version 3 X.509 certificates,generators for Version 2 X.509 attributecertificates, PKCS12 support, and APIs for dealingwith S/MIME, CMS, OCSP, TSP, OpenPGP, and TLS.Versions are provided for the J2ME, and JDK1.0-1.6.License: Freely DistributableChanges:
This release adds certifications with userattributes for OpenPGP, CMS countersignaturesupport, and VMPC-MAC. Speed improvements havebeen made to the ASN.1 package. The CertPathvalidator now covers a wider range of NISTvalidation tests. An error in IV handling for SEEDand Camellia in CMS has been fixed. Other bugfixes and enhancements were made. The signingcertificate for the provider has been updated toone expiring in 2013.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT LINUX

dacs.java

DACS.JAVA(7)						  DACS Miscellaneous Information					      DACS.JAVA(7)

NAME

       dacs.java - DACS Java support

DESCRIPTION

       This document describes support for Java provided by DACS.

       To enable Java support, DACS must be configured using the --enable-java flag. It may also be necessary to specify the location of the Java
       commands and include files. See dacs.install(7)[1].

	   Note
	   Java support is currently very limited and should be considered experimental. It is currently only possible to call dacsauth(1)[2] and
	   dacscheck(1)[3] using the Java Native Interface (JNI) provided. The command line arguments to both of these commands are exactly as
	   documented in their manual pages. Each argument is passed as a String.

	   The code is not thread-safe and is probably not suitable for being called many times within a particular process due to assumptions it
	   makes about dynamic memory allocation.

	   There are no immediate plans to improve or extend Java support. Using the existing capability to build the JNI layer, however, it
	   should not be difficult for an experienced Java programmer to build upon the example Java code provided.

       With Java support enabled, building DACS will copy the JNI shared library and a .jar file to the library directory (default:
       /usr/local/dacs/lib), and the JNI include files to the include directory (default: /usr/local/dacs/include).

       The tools/java/jni distribution directory contains a simple script called javarun that demonstrates how to run dacsauth or dacscheck as a
       Java application. For example, to validate the Unix password for user somebody, run (as root):

	   ./javarun dacsauth -m unix suff -user somebody -prompt

DIAGNOSTICS

       The return codes are as documented in the command's manual page.

AUTHOR

       Distributed Systems Software (www.dss.ca[4])

COPYING

       Copyright2003-2012 Distributed Systems Software. See the LICENSE[5] file that accompanies the distribution for licensing information.

NOTES

	1. dacs.install(7)
	   http://dacs.dss.ca/man/dacs.install.7.html

	2. dacsauth(1)
	   http://dacs.dss.ca/man/dacsauth.1.html

	3. dacscheck(1)
	   http://dacs.dss.ca/man/dacscheck.1.html

	4. www.dss.ca
	   http://www.dss.ca

	5. LICENSE
	   http://dacs.dss.ca/man/../misc/LICENSE

DACS 1.4.27b							    10/22/2012							      DACS.JAVA(7)