Package net.rim.device.api.crypto.cms

Cryptographic Message Syntax (CMS) Classes and Definitions.


Interface Summary
CMSContentTypes The content types that the RIM version of CMS supports.
CMSEnvelopedDataConstants This interface contains a series of constants that are used by the CMSEnvelopedDataInputStream and CMSEnvelopedDataOutputStreams

Class Summary
CMSAttribute Represents an attribute that may be found/placed in a CMS message.
CMSCompressedDataInputStream Implements a CMS compressed data input stream so that a message that has been compressed in the CMS format can be properly parsed and decompressed.
CMSCompressedDataOutputStream Implements a CMS Compressed data output stream so that outgoing data can be compressed and formatted as per CMS compressed data messages.
CMSContext Implements a "two stage" method of processing CMS messages.
CMSDataInputStream Implements a CMS data input stream.
CMSDataOutputStream Implements a CMS data output stream so that outgoing data can be written to the output stream.
CMSEntityIdentifier This class encompasses how entities ( whether recipients or signers ) are represented in CMS.
CMSEnvelopedDataInputStream Defines an input stream to parse a CMS enveloped message.
CMSEnvelopedDataOutputStream Defines a CMS enveloped data output stream to handle a CMS enveloped data message.
CMSInputStream A generic CMS input stream that the data, signed, and enveloped input streams extend.
CMSOutputStream A generic CMS output stream that all specific CMS output streams extend.
CMSReceiptData A class containing information required to verify a signed receipt.
CMSReceiptRequest A CMSReceiptRequest allows the user to create a signed receipt request and add it to a CMSSignedDataOuptutStream.
CMSSignedDataInputStream Implements a CMS signed data input stream so that a message that has been signed in the CMS format can be properly parsed and verified.
CMSSignedDataOutputStream Implements a CMSSigned data output stream so that outgoing data can be signed and formatted as per CMS signed data messages.
CMSSignedReceiptInputStream A CMSSignedReceiptInputStream allows the user to read in a signed receipt and process it properly.
CMSSignedReceiptOutputStream A CMSSignedReceiptOutputStream allows the user to properly create a signed receipt.
CMSSigner Groups together a signature signer and a group of certificates for use by CMS.
EMSAcceptRequestInputStream A EMSAcceptRequestInputStream allows the user to read in a certificate accept request from an EMS (Entrust Messaging Server).
EMSAcceptResponseOutputStream A EMSAcceptResponseOutputStream allows the user to properly create an EMS(Entrust Messaging Server) Certificate Accept Response message.

Exception Summary
CMSDecryptionException Thrown when an error occurs while decrypting a CMS message.
CMSException Thrown when a CMS error occurs.
CMSNoCertificateFoundException Thrown when no certificate can be found, in the message or in the key store, that matches the certificate specified in the message.
CMSNoPrivateKeyFoundException Thrown when something is attempted to be decrypted but no private key can be found.
CMSNoPublicKeyFoundException Thrown when no public key can be found to verify a signature on a message.
CMSNoReceiptDataFoundException Thrown when the original message cannot be found to verify a signed receipt.
CMSNoSuchAlgorithmException Thrown when no matching algorithm can be found to carry out a desired task.
CMSNoSuchEntityException Thrown when no CMSEntity can be found in the message.
CMSParsingException Thrown when a malformed CMS message is parsed.
CMSVerificationException Thrown when the signature on a CMS signed message cannot be verified.

Package net.rim.device.api.crypto.cms Description

Cryptographic Message Syntax (CMS) Classes and Definitions.

CMS describes an encapsulation syntax for data protection. It supports digital signatures, message authentication codes (MACs), and encryption.

The syntax allows recursion, such that one "envelope" can be nested within another. This way, a second party can sign data that was previously signed and enveloped by a previous party. In addition to the content of the message, other attributes such as signing time, signatures, and sub-signatures (attributes of a signature) can also be authenticated.

This package contains RIM's implementation of the CMS standard. These standards are outlined in RFC 2630. We also support RFC 3278, 3211, 3217, 3274, the AES draft standard , the RSA-OAEP draft standard , and the Signed Receipt part of RFC 2634.

Copyright 1999-2010 Research In Motion Limited. 295 Phillip Street, Waterloo, Ontario, Canada, N2L 3W8. All Rights Reserved.
Copyright 1993-2003 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California, 94303, U.S.A. All Rights Reserved.
Copyright 2002-2003 Nokia Corporation All Rights Reserved.
Java is a trademark of Sun Microsystems, Inc.