Home >> All >> hk >> hku

•	hk.hku.cecid.* (27)	•	hk.hku.cecid.phoenix.* (27)
•	hk.hku.cecid.phoenix.common.* (9)	•	hk.hku.cecid.phoenix.common.util.* (9)
•	hk.hku.cecid.phoenix.pki.* (18)

Package Samples:

• hk.hku.cecid.phoenix.common.util
• hk.hku.cecid.phoenix.pki

Classes:

• XMLProperty: This is a concrete implementation of the property object for loading and saving the property content into a XML-based file. The file is assumed to be rooted by a "Property" element. And the get/set path is simplified XPath, with "/" as separator. For example, a path of "A/B/C" and value of "test" creates a tree like: <Property>    <A>    <B>      <C>test</C>    </B>   </A> </Property>
• CompositeKeyStore: Composite keystore which manages keystores of different types. A typical Java keystore supports only one keystore type per file. That will be inconvenient for applications to manage several types of keystore. Also, this composite keystore supports managing multiple keystore files. This can be viewed as a keystore registry, that is, this object manages a pool of keystore files.
• AuthenticationManager: This class manages a password file for doing user authentication. The user and password pair will be stored using the following format: user1:password1 user2:password2 The passwords stored is the message digest of the real password generated using MD5 algorithm. Also, the output the MD5 algorithm is then Base64 encoded before writing the the password file.
• SMIMEHandler: It is the base class of SMIMEEncrypter and SMIMEDecrypter. The BouncyCastle 's SMIME engine only works properly with BouncyCastle 's JCE provider. The subclass should call the method initiate(), which add the BouncyCastle 's Provider and setup which DataHandler for what types of content type.
• ApacheXMLDSigner: This class hides the details for digital signature. The digital signature routines are provided by the Apache XML Security library. We defined a standard way to have the document signed as interface. Different classes will implement the interface using different library behind.
• CertPathVerifier: This class wraps the certificate path verification routine into a separate static method. This is useful when JDK1.3 is used, the cert path verification is skipped. And the JDK1.4 specific classes will not be loaded, as they are all called in this class.
• Property: This is an abstract class for property file reader. We may implement XML based, or plain text based, or encrypted property file reader out of this abstract class. This interface is defining some common methods needed by all kinds of property readers.
• JDKLogger: This is the implementation class for logging using JDK 1.4 library. The super class of this class shields the complexity for using JDK1.3 or JDK1.4, using log4j or JDK Logging API. All configuration information are read from properties file.
• Log4JLogger: This is the implementation class for logging using log4j library. The super class of this class shields the complexity for using JDK1.3 or JDK1.4, using log4j or JDK Logging API. All configuration information are read from properties file.
• CRLSource: This is an abstract class for holding a X509 CRL instance. The functionality of CRL is given by this class. The sub-classes will provide different initialization method for loading the CRL, for example, through a file or through LDAP.
• SMIMEEncrypter: A generator of SMIME encryption. It only works properly with BouncyCastle 's JCE provider. Currently it only supports 168bit triple DES with CBC for encrypting the body parts. The DES key, which is a symmetric key, is encrypted by RSA.
• KeyStoreFileProp: This class represents the data structure for holding parameters for accessing a keystore file. Since the parameters will be serialized to the file system, some fields (particularly password will be scrambled.
• Logger: This is a wrapper class for logging. This class shields the complexity for using JDK1.3 or JDK1.4, using log4j or JDK Logging API. All configuration information are read from properties file.
• TextProperty: This is a concrete implementation of the property object for loading and saving the property content into a text-based file. The format used is exactly the same of Java properties file.
• XMLDSigner: This interface defines a standard way to have the document signed. Different classes will implement the interface using different library behind.
• CertSource: This class loads a X509 certificate file. Basically this class only acts as a convenience wrapper of java.security.cert.X509Certificate.
• DocumentResolver: This class is needed by the Apache XML Security library for locating and loading the document attachments.
• CRLFileSource: This class extends CRLSource to add initialization procedure for loading a file-based CRL.
• PassTool: A command line utility to manipulate the password file used by AuthenticationManager.
• VerifyException: Exception class representing the error during verification of digital signature.
• StoreException: Exception class representing the error during storing the composite keystore.
• SignException: Exception class representing the error during signing the digital signature.
• SMIMEException: The exception will be thrown when generating SMIME mime body or mime message
• DocumentDetail: A data structure class for holding the document attachment parameters.
• SMIMEDecrypter: A class for decrypting MimeBodyPart that was encrypted by SMIME.

Home | Contact Us | Privacy Policy | Terms of Service