JAVA Toolkit
| home | contact




archive

Versions History

IAIK-CMS 5.0 - 20. December 2013

Class or Package

Bug / Change New Feature

Description and Examples

*

C

JDK 1.1.x is no longer supported. Supported Java(TM) versions are
1.2, 1.3, 1.4, 1.5 (5.0), 1.6 (6.0), 1.7 (7.0) and compatible.

*

C

Adapted to latest Internet Standard versions of CMS and S/MIME: RFC 5652 (CMS)
and RFC 5751 (S/MIME Version 3.2)

demo.cms.ecc.*, demo.smime.ecc*

C

Adapted for use with new IAIK ECC library IAIK-EccelerateTM.

iaik.cms.CMSAlgorithmID

C

changed implementation names for some ALgorithmIDs (aes192_CBC: from "AES/CBC/PKCS5Padding" to "AES192/CBC/PKCS5Padding", aes256_CBC: from "AES/CBC/PKCS5Padding" to "AES256/CBC/PKCS5Padding", cms_aes192_wrap: from "AESWrapAES" to "AES192WrapAES192", cms_aes256_wrap: from "AESWrapAES" to "AES256WrapAES256", cms_camellia192_wrap: from "CamelliaWrapCamellia" to
"Camellia192WrapCamellia192", cms_camellia256_wrap: from "CamelliaWrapCamellia" to "Camellia256WrapCamellia256")

iaik.cms.AuthenticatedDataOutputStream, iaik.cms.AuthEnvelopedDataOutputStream, iaik.cms.CompressedDataOutputStream, iaik.cms.DigestedDataOutputStream, iaik.cms.EnvelopedDataOutputStream, iaik.cms.SignedDataOutputStream,

C

added stream closing check to write and flush methods

iaik.cms.CMSAttribute,
iaik.cms.CMSAttributes

C

Concrete attribute value implementation (if available) is not created/initialized
before getAttributeValue(s) is called.

iaik.cms.KeyTransRecipientInfo, iaik.cms.KeyAgreeRecipientInfo

C

Method decryptKey allows null as PrivateKey (may be useful for HSM based decryption).

iaik.cms.IaikProvider

C

Method verifySignatureFromHash uses the IAIK-JCE RAWRSASSA_PKCS1_V15 Signature engine to handle PKCS1#v15 signatures containing digest algorithms with
both absent and NULL parameters.

iaik.cms.SecurityProvider

C

Method verifySignatureFromHash decodes the PKCS#1 DigestInfo instead of
encoding it to handle PKCS1#v15 signatures containing digest algorithms with
both absent and NULL parameters.

iaik.cms.SecurityProvider

NF

Method getSignature(String algorithm, int mode, Key key, AlgorithmParameterSpec paramSpec) added to allow parameter based Signature engine intialization.

iaik.cms.SecurityProvider

NF

Method getKeyLength(Key key) added to allow provider independent calculation of key length.

iaik.cms.SecurityProvider,

iaik.cms.IaikEccProvider

C

Method calculateSharedSecret added to calculate a shared secret between two parties using a specific KeyAgreement algorithm.

iaik.cms.SecurityProvider

C

getSignature() calls getSecureRandom() to get the SecureRandom for initializing the JCA Signature engine

iaik.cms.SecurityProvider

C

getMicAlgs now supports OID strings as micalg parameters for the most well known hash algorithms

iaik.cms.SignedDataStream

MF

Method removeMessageDigest added.

iaik.cms.SignerInfo

C

Method getSigningCertificateAttribute, getSigningCertificateV2Attribute:
check if only one SigningCertificate, SigningCertificateV2 attribute is present and if they are single-valued.

iaik.cms.SignerInfo

C

Constructors with signer certificate added to allow automatic
algorithm derivation from public key.

iaik.cms.SignerInfo

C

Adapted automatic algorithm selection to NIST SP 800-57; default hash algorithm now is SHA-256

iaik.cms.SignerInfo

B

toASN1Object: Fixed signature algorithm NULL/absent parameter encoding.

iaik.cms.CompressedDataStream, iaik.cms.EnvelopedDataStream, iaik.cms.EncryptedContentInfoStream, iaik.cms.SignedDataStream

C

toASN1Object: allows definite length encoding

iaik.smime.BufferedLineInputStream

C

read tries to read from the underlying stream if less then the requested number of bytes are available in the buffer

iaik.smime.SignedContent, iaik.smime.SMimeContent

C

Method setBlockSize added to allow definite length encoding.

iaik.smime.SignedContent, iaik.smime.SMimeContent

C

Workaround in method setDataHandler to avoid problems with JavaMail 1.5 when setting the DataHandler of an existing MimeMessage/MimeBodyPart as DataHandler for a new MimeMessage/MimeBodyPart. The problem is fixed in version 1.5.1 of JavaMail
(see JavaMail bug report).

iaik.smime.SignedContent,

iaik.smime.SMimeSigned
iaik.smime.SMimeUtil

C

SigningCertificate/SigningCertificateV2 attribute added to the default signed attributes where applicable. AES-256-CBC and AES-128-CBC added to the default SMIME capabilities
attribute

iaik.smime.SMimeSigned,

iaik.smime.SMimeContent

C

SHA-1/rsaEncryption defaults removed (if not explicitly set, digest and signature algorithm are derived from the signer key algorithm).

iaik.smime.SMimeSigned

NF

addSigner methods with signer certificate added to allow automatic algorithm derivation from public key.

iaik.smime.ess.MLReceiptPolicy

B

Implements the Cloneable interface. Fixed equals method.

iaik.smime.ess.ReceiptContent

B

Fixed MsgSigDigest attribute calculation in method setSigner.

iaik.smime.ess.utils.KeyStoreDatabase

B

Fixed certChain null check in method addKey.

iaik.smime.ess.utils.SignedReceipt

B

Fixed address list calculation in method getReceiptsToAddressList.

iaik.smime.ess.SigningCertificate(V2)

C

decode keeps ASN.1 structure to keep ASN.1 structure to can verify signatures with SigningCertificateV2 attributes that contain an invalid DER encoded ESSCertIDv2 object (default hash algid included)

 

IAIK-CMS 4.1 - 16. October 2009

Class or Package

 Bug / Change New Feature

Description and Examples

*

C

Where possible Hashtables are replaced by HashMaps to increase access performance especially
 in multithreaded environments; for JDK 1.1.x a new jdk11x_update.jar version must be used

demo.smime.ecc.SMimeEccSuiteBDemo

NF

Demo showing how to use the S/MIME library with the NSA Suite B algorithm suite (RFC 5008)

iaik.cms.ecc.IaikEccProvider

NF

Support for the dhSinglePass_stdDH_sha256kdf_scheme and dhSinglePass_stdDH_sha384kdf_scheme
 key encryption schemes as required by the NSA Suite B S/MIME algorithm suite (RFC 5008)

iaik.cms.AuthenticatedData,

 iaik.cms.AuthenticatedDataStream,

 iaik.cms.AuthenticatedDataOutputStream

NF

Support for HMACwithAESwrap key wrap algorithm (RFC 3537).

iaik.cms.AuthEnvelopedData,

 iaik.cms.AuthEnvelopedDataStream,

 iaik.cms.AuthEnvelopedDataOutputStream

NF

Implementation of the Authenticated-Enveloped-Data Content Type according to RFC 5083 for authenticated
 content encryption using AES-CCM or AES-GCM (RFC 5084).

iaik.cms.ContentInfo

B

Fixed EOC parsing

iaik.cms.Data,

 iaik.cms.EncapsulatedContentInfo

C

Uses DerCoder for content parsing to support arbitrary nested octet strings

iaik.cms.EncryptedContentInfo,

 iaik.cms.EnvelopedData

C

setInputStream now read the stream instead of throwing an "Method not supported" exception

iaik.cms.EncryptedContentInfoSream

C

Additional setupCipher methods (required for AuthEnvelopedData type support)

iaik.cms.EncryptedData,

 iaik.cms.EncryptedDataStream,

 iaik.cms.EncryptedDataOutputStream

NF

Support for Camellia cipher algorithm added (RFC 3657).

iaik.cms.EnvelopedData,

 iaik.cms.EnvelopedDataStream,

 iaik.cms.EnvelopedDataOutputStream,
 iaik.smime.EncryptedContent

NF

Support for Camellia cipher and Camellia key encryption algorithm added (RFC 3657).

iaik.cms.IaikProvider

NF

When used with the unltd version of IAIK-JCE (v3.17 or later), IAIK-CMS can be used with unlimited strength
 cryptography even if only the default jurisdiction policy files are installed.

iaik.cms.OtherRecipientInfo

B

getEncryptedKey: fixed recursive call

iaik.cms.SecurityProvider

NF

getAuthCipherEngine methods and AuthCipherEngine interfaces added;
 used for Authenticated-Enveloped-Data Content Type support (RFC 5083)

iaik.cms.SignedDataStream

NF

decode: Now also can handle an empty content OCTET STRING
 if included in explicit mode (some applications erronously may include an empty OCTET
 STRING instead of omitting the eContent field)

iaik.cms.SignerInfo,

 iaik.cms.SignedData,

 iaik.cms.SignedDataStream,

 iaik.cms.SignedDataOutputStream,

 iaik.smime.SignedContent

NF

Added SHA-2 support for Digital Signature Algorithm (DSA) specified by FIPS PUB 186-3.

 Added support for ECDSA plain variant according to German BSI Technical Guideline TR-03111.

iaik.cms.SignerInfo

NF

verifySignature: If signature verification fails with the given signed attributes
 try a second time with sorted attributes

iaik.cms.SignerInfo

C

Automatic digest- and/or signature algorithm derivation (if not explcitly set) now
 also considers RSA-PSS, DSA with SHA-2 and ECSDA with SHA-2

iaik.cms.SignerInfo

B

Fixed version number setting in constructor

SignerInfo(signerIdentifier, digestAlgorithm, signatureAlgorithm, privateKey)

iaik.cms.TrustVerifier

NF

verifyChain: check that different consecutive certificates do not have the same signature value
 (countermeasure against preimage attacks on the signature hash algorithm)

iaik.smime.SMimeParameters

NF

New method setCommandMap allowing to set a MailcapCommandCap for locale use
 without changing the system-wide default command map (see the Javadoc guidelines for
 using this method).

 

IAIK-CMS 4.01 - 21. December 2007

Class or Package

 Bug / Change New Feature

Description and Examples

ECC

NF

 Support for ECDSA with SHA224, SHA256, SHA384, SHA512, RIPEMD160 added; requires version 2.16 (or later)
 of the IAIK-ECC provider

iaik.smime.SignedContent

B, C

micalg header update done already when adding a signer (to be recognized by any JavaMailTM version)

 

 

IAIK-CMS 4.0 - 20. September 2007

Class or Package

 Bug / Change New Feature

Description and Examples

demo.cms.*, demo.smime.*

NF

 Demos showing how to use the IAIK-ECC and IAIK-PKCS#11 libraries with
 IAIK-CMS to use ECDSA, ECDH and smartcards with CMS/SMIME, respectively.
 A lot of further demos added. CMS demos splitted according to content
 type membership.

 iaik.cms.SignedDataOutputStream,
 iaik.cms.EnvelopedDataOutputStream,
 iaik.cms.DataOutputStream,
 iaik.cms.AuthenticatedDataOutputStream,
 iaik.cms.EncryptedDataOutputStream,
 iaik.cms.DigestedDataOutputStream,
 iaik.cms.CompressedDataOutputStream
 iaik.cms.ContentInfoOutputStream

NF

 OutputStream based implementations of the several CMS content types to encode the CMS object during the application write the content data to an output stream, e.g.:
 

// the output stream to which to write the signed data
OutputStream resultStream = ...
    
// create SignedDataOutputStream
int mode = SignedDataOutputStream.IMPLICIT;
SignedDataOutputStream signedData = 
  new SignedDataOutputStream(resultStream, mode);
...    
// add certificates, SignerInfos...
...
// write in the data to be signed
byte[] buffer = new byte[2048];
int bytesRead;
while ((bytesRead = dataInputStream.read(buffer)) != -1) {
  signedData.write(buffer, 0, bytesRead);
}
// closing the stream adds the signer infos
signedData.close();

iaik.cms.AuthenticatedDataStream

B

Fixed getAuthenticatedAttributes; accidently returned authenticated attributes

 iaik.cms.AuthenticatedDataStream,
 iaik.cms.AuthenticatedData

B

  toASN1Object: unauthenticated attributes tagged with number 3

iaik.cms.ContentInfo

C, NF

 Does no more keep encoded content by default; static method keepEncodedContent 
 may be used to enforce to change the default behaviour and keep the encoded content

 iaik.cms.ContentInfo,
 iaik.cms.ContentInfoStream

C

Changed content type implementation class registration so that classes are not loaded before actually needed

iaik.cms.CounterSignature

B, C

Fixed recursive call in methods get(Un)signedAttributes, methods add(un)SignedAttribute, getUnsignedAttributeValue added

iaik.cms.EncryptedDataStream

NF, C

Additional setupCipher methods; default iteration count for pbe encryption set to 2000

 iaik.cms.DigestedDataStream,
 iaik.cms.DigestedData

NF

Method setInputStream, setContent, respectively, added

iaik.cms.EncryptedContentInfo(Stream)

C

If not set, tries to get the name of the cek name from the content encryption algorithm to avoid problems due to jurisdiction policy checks

iaik.cms.IaikCCProvider

NF

CMS SecurityProvider for use with the Common Criteria evaluated IAIK-JCE versions, IAIK-JCE 3.1CC, IAIK-JCE 3.15CC

iaik.cms.IaikEccProvider

NF

CMS SecurityProvider for using the IAIK-ECC library to encrypt CMS and S/MIME messages based on ECDH

iaik.cms.OutputStreamCompressEngine

NF

OutputStreamCompressEngine for use with CompressedDataOutputStream added

iaik.cms.OutputStreamMacEngine

NF

OutputStreamMacEngine for use with AuthenticatedDataOutputStream added

iaik.cms.RecipientEncryptedKey

NF

AES key wrap added

iaik.cms.SecurityProvider

B

  checkDomainParameters: fixed getting algorithm id from public key

iaik.cms.SecurityProvider

NF

Method getOriginatorPublicKey added to parse the OriginatorPublicKey of a KeyAgreeRecipientInfo, if present

iaik.cms.SecurityProvider

NF

Method getOutputStreamCompressEngine added for use with CompressedDataOutputStream

iaik.cms.SecurityProvider

NF

Method getOutputStreamMacEngine added for use with AuthenticatedDataOutputStream

iaik.cms.SecurityProvider

NF

  verifySignatureFromHash: countermeasure against Bleichenbacher RSA signature forgery attack against signature value garbage when keys with public exponents of 3 are used (when not using IAIK-JCE 3.142 or later for RSA PKCS#1v1.5 signatures)

iaik.cms.SecurityProvider

C

Changed Attribute implementation class registration so that classes are not loaded before actually needed

 iaik.cms.SignedDataStream,
 iaik.cms.SignedData

NF

New method getCertificates(CertificateIdentifier) to get the (sorted) certificate chain of some specific signer, if included

iaik.cms.SignerInfo

C

  get(Un)SignedAttributes: return empty array if no attributes are included

iaik.cms.SignerInfo

C

Constructor with digest algorithm only does not set the signature algorithm automatically to rsaEncryption; rather it tries to derive the signature algorithm (and digest algorithm -- if not set) from the private key algorithm

iaik.cms.SignerInfo

NF

 Support for SigningCertificateV2 attribute (methods getSigningCertificateV2Attribute,

isSignerCertificate)

iaik.smime.BinaryCanonicalizer

NF

New canonicalizer that does not canonicalize the contents; to be used in environments where no canonicalization is needed, for instance when transfering multipart/signed S/MIME messages over HTTP (as, e.g., done by AS2)

iaik.smime.EncryptedContent

NF

Method setupCipher added to allow an application to initialize the cipher for decryption with the (already decrypted) symmetric content encryption key

iaik.smime.SignedContent

C

Performance improvements by using new buffering and canonicalization meachanisms

iaik.smime.SMimeParameters

NF

New method setTempDirectory allows to configure a temporary directory to avoid memory problems by temorarily writing contents to a file during message processing

 iaik.smime.SharedFileInputStream,
 iaik.smime.SharedByteArrayInputStream

NF

New shared streams used for performance improvements

iaik.smime.ess.MLData

B

Fixed equals method

 iaik.smime.ess.ESSCertIDv2,
 iaik.smime.ess.SigningCertificateV2

NF

Implementation of RFC 5035 to support hash algorithm agility for the SigningCertificateV2 attribute

 

 

IAIK-CMS 3.2 Final - 11. February 2005

Class or Package

 Bug / Change New Feature

Description and Examples

demo.cms.*

NF

Demos showing how to use the IAIK-ECC and IAIK-TSP libraries with IAIK-CMS to use ECDSA as signaure algorithm and adding a TimeStampToken attribute to a SignedData object, respectively.

demo.smime.ess.*

NF

SecurityLabel and SigningCertificate attribute demos added.

iaik.cms

NF

Adopted to most recent standard specification (RFC 3852)

iaik.cms.CertificateSet

B

Fixed tag in AttributeCertificate encoding.

iaik.cms.SignerInfo

B

Parameters field must be absent only for DSA in encoding of signature algorithm (not for ECDSA).

iaik.smime

NF

Adopted to most recent standard specification (RFC 3851)

iaik.smime.encrypted_content

B,C

If header parsing failes, tries to parse content type from encoding.

iaik.smime

C

SignedContent, EncryptedContent, CompressedContent: Allow/Recommend to call methods setContentHeaders/setContentContentTransferEncoding before setting the content (to avoid header update overhead during the saveChanges run).

 

 

IAIK-CMS 3.1 Final - 1. July 2004

Class or Package

 Bug / Change New Feature

Description and Examples

All

NF, B, C

A lot of changes and new features, some bug fixes throughout the library. Full ESS (Enhanced Security Services, RFC 2634) support added. Authenticated-data content type and Compressed-data content type (RFC 3274) added. PasswordRecipientInfo (RFC 3211) and OtherRecipientInfo added. S/MIMEv3.1 ContentType application/pkcs7-mime compressed-data added. New SDSEncodeListener interface allows to update (e.g. add attributes like time stamp or counter signature) a SignedDataStream during the encoding phase (also when verifying and encoding an already existing SignedData again). Improved attribute handling.

 

 

IAIK-CMS 3.0 Beta 1- 18. May 2001

Class or Package

 Bug / Change New Feature

Description and Examples

demo.cms

NF

CMS demo examples

demo.smime

NF

S/MIME demo examples

iaik.cms

NF

Implements the Cryptographic Message Syntax (CMS, RFC 2630); succeeds the PKCS#7 library of IAIK-JCE

iaik.smime

NF

Implements the S/MIME Version 3 standard; succeeds IAIK-S/MIMEv2

 

 

IAIK-S/MIME2.6 Final - 30. June 2000

Class or Package

 Bug / Change New Feature

Description and Examples

demo.*

NF, C

The demo class files have been separated from the library. Now the following jar files are available: iaik_smime.jar and iaik_smime_demo.jar.

 

 

IAIK-S/MIME 2.6 Beta 1 - 23. December 1999

Class or Package

 Bug / Change New Feature

Description and Examples

iaik.security.smime.Canonicalizer

NF

Interface that allows an application to implement its own canonicalization strategy. The canonicalization scheme will come into effect when activating the new Canonicalizer by calling the static setCanonicalizer method of class SMimeParameters. Ougoing messages are processed by the Canonicalizer when modelling body parts and multiparts by classes SMimeBodyPart and SMimeMultipart or when setting the text of a multipart/signed message by method setText of class SignedContent. Ingoing multipart/signed messre also processed by the canonicalizer.

iaik.security.smime.SMimeParameters

NF

New method setCanonicalizer for enabling an application-written canonicalizer.

iaik.security.smime.DefaultCanonicalizer

NF

Default implementation of the Canonicalizer interface for ensuring that and only appaer together as for non binary entities. On ougoing messages only enabled when modelling body parts and multiparts by classes SMimeBodyPart and SMimeMultipart or when setting the text of a multipart/signed message by method setText of class SignedContent. On ingoing messages only used for the contents part of multipart/signed messages.

iaik.security.smime.EncryptedContent

NF

New method setContentContentTransferEncoding for allowing to explicitly set the content transfer encoding of the inner content. This method may be useful, for instance, when setting the content by means of method setText and wishing to apply another content transfer encoding than allocated by the JavaMail™ API.

iaik.security.smime.EncryptedContent

NF

New method getRecipientInfoIndex(X509Certificate recipientCertificate) for searching for the recipient index belonging to the recipient certificate.

iaik.security.smime.EncryptedContent

B

Content with another content transfer encoding than 7bit, 8bit may have not been encoded as desired.

iaik.security.smime.JMailSigned

C

Only extends class SMimeSigned to be used for SignedContent to ensure that for a multipart/signed message the content body is piped through the DigestStream before writing the signature. Allows to use SMimeSigned without dependence on JavaMail™ code.

iaik.security.smime.pkcs10_content

NF

DataContentHandler for type application/pkcs10 to handle certificate request messages.

iaik.security.smime.PKCS10Content

NF

Class for sending and parsing application/pkcs10 messages conatining a PKCS#10 certification request.

iaik.security.smime.SignedContent

NF

New method setContentContentTransferEncodingfor allowing to explicitly set the content transfer encodingof the inner content. This method may be useful, for instance,when setting the content by means of method setText and wishingto apply another content transfer encoding than allocated bythe JavaMail™ API.

iaik.security.smime.SignedContent

B

Content with another content transfer encodingthan 7bit, 8bit may have not been encoded as desired.

iaik.security.smime.SignedContent

C

Multipart/signed messages where the contentsitself is composed of parts have to be built with classes SMimeBodyPartand SMimeMultipart for ensuring proper canonicalization.

iaik.security.smime.SMimeBodyPart

NF, C

New Constructor SMimeBodyPart to be used forcreating body parts for multipart/signed messages.

iaik.security.smime.SMimeBodyPart

C

If the SMimeBodyPart representing the first (contents)part of a multipart/signed message contains a multipart noweach of the body parts of this multipart separately is canonicalized.

iaik.security.smime.SMimeEncrypted

NF

New method getRecipientInfoIndex(X509CertificaterecipientCertificate) for searching for the recipient indexbelonging to the recipient certificate.

iaik.security.smime.TrustVerifier

NF

New class allowing simple certificate verifying,trust checking and check of Email addresses of From: headerand certificate.

demo.smime.keystore

NF

Special keystore files (SMimeKeyStore, SetupSMimeKeyStore,SMimeKeyStoreConstants)used by the IAIK-S/MIME demos to distinguish between signingandencryption certificates.

 

 

IAIK-S/MIME 2.52 - 11. August 1999

Class or Package

 Bug / Change New Feature

Description and Examples

iaik.security.smime

B

When no or only one certificate is included, a wrong hash may have been sent within the authenticated attributes; and therefore verification must fail.

iaik.security.smime.SignedContent

B

Method getContentInputStream has not returned the message as required.

iaik.security.smime.SMimeParameters

NF

Allows to decide whether to use old (starting with an "x") or new S/MIME content types when creating a new S/MIME message.

iaik.security.smime.SignedContent

B

When parsing a message now the new S/MIME content types are also recognized.

iaik.security.smime.SignedContent

B

When parsing a message where the content-transfer-encoding is binary or 8Bit, no Base64 decoding is performed.

iaik.security.smime.CanonicalizeOutputStream

B

A single 0x0D now also is forced to 0x0D 0x0A.

iaik.security.smime.SignedContent

NF

Setting of smime-type parameter ("signed-data", "certs-only"); creating of certs-only messages;

iaik.security.smime.SignedContent

NF

New method setHeaders(Message) for setting content-disposition and filename parameters for implicit messages (in equivalence to EncryptedContent)

iaik.security.smime.SignedContent

NF

New methods setCRLs(..) and getCRLs() for setting/getting the SignedData´s crls field

iaik.security.smime.EncryptedContent

NF

New Method setSMimeType() for setting the smime-type parameter ("enveloped-data"

 

 

IAIK-S/MIME 2.51 Maintenance Release - 15. June 1999

Class or Package

 Bug / Change New Feature

Description and Examples

iaik.security.smime.SignedContent

B

A nullpointer exception or misleading verification error message may occur when parsing a data source returning no smime-type. This has been fixed.

iaik.security.smime.EncryptedContent

B

When using the setDataHandler(...) method for supplying a multipart object the body headers had not been updated accurately. This has been fixed.

 

 

IAIK-S/MIME 2.5 - 30. April 1999

Class or Package

 Bug / Change New Feature

Description and Examples

iaik.security.smime

NF,C,B

Now detached from the IAIK-JCE toolkit and available as own distribution. Several bugs fixed. Gerneral support for certs-only messages for distributing certificates.

iaik.security.smime.SMimeMailer

NF

A simple class for sendingS/MIME emails.

demo

NF

Redisigned demo library.

 

 

IAIK-JCE 2.5 beta1 - 23. December 1998

Class or Package

 Bug / Change New Feature

Description and Examples

iaik.security.smime

NF

Now support for the Sun.javax.mail.API. The following types of e-mails are supported: signed, encrypted, signed and encrypted

 

 

IAIK-JCE 2.0 Beta2 - 2. February 1998

Class or Package

 Bug / Change

New Feature

Description and Examples

iaik.security.smime

NF

Package for dealing with S/MIME messages.At this time only S/MIME encrypted is implemented.

 

 
print    tip a friend
back to previous page back  |  top to the top of the page