Differences between revisions 1 and 2
Revision 1 as of 2006-03-14 09:29:06
Size: 1585
Comment: status page for the crypto component
Revision 2 as of 2009-09-20 21:55:27
Size: 1591
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
Check the ["component development status"] page for the status of other ClassLibrary modules. Check the [[component_development_status]] page for the status of other ClassLibrary modules.
Line 8: Line 8:
Component is temporarily included into ["SECURITY"] module. Component is temporarily included into [[SECURITY]] module.
Line 38: Line 38:
When crypto functionality is necessary one may use open source [http://www.bouncycastle.org BouncyCastle] provider When crypto functionality is necessary one may use open source [[http://www.bouncycastle.org|BouncyCastle]] provider
Line 42: Line 42:
Signed jar file verification requires some crypto algorithms. But [http://www.bouncycastle.org BouncyCastle] provider is located in a signed jar file. Signed jar file verification requires some crypto algorithms. But [[http://www.bouncycastle.org|BouncyCastle]] provider is located in a signed jar file.
Line 44: Line 44:
verify signature in [http://www.bouncycastle.org BouncyCastle] jar. verify signature in [[http://www.bouncycastle.org|BouncyCastle]] jar.

Overview

CRYPTO - javax.crypto, javax.crypto.interfaces, javax.crypto.spec

Status

Check the component_development_status page for the status of other ClassLibrary modules.

Component is temporarily included into SECURITY module.

J2SE 1.4.2

The current codes cover J2SE 1.4.2 API

Java 5.0

Current code is mostly compliant with J2SE 1.5 specification. It should be updated to reflect new Java 5.0 enhancements (e.g. generics, enums) when harmony has a 1.5 compatible VM

Below are some details about what's available, missing and in progress

Public API

This component contains implementation of public API, internal code and unit tests. All public 1.5 classes are implemented and tested..

The code contains a number of TODO's such as:

  • switch to generics and/or enums
  • use more efficient API introduced in 1.5
  • implement optional features

Security Providers

There is no JCE providers implemented in Harmony.

When crypto functionality is necessary one may use open source BouncyCastle provider

Known issues:

Signed jar file verification requires some crypto algorithms. But BouncyCastle provider is located in a signed jar file. So, at least Message Digest SHA-1 and Signature SHA1withDSA should be implemented and placed into unsigned jar to verify signature in BouncyCastle jar.

Tools

No crypto related tools (e.g. keytool, jarsigner) are currently implemented.

CRYPTO (last edited 2009-09-20 21:55:27 by localhost)