The Java Community Process(SM) Program - JSRs: Java Specification Requests

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy

JSR #321
Trusted Computing API for Java^TM
Public Review Ballot
Ballot duration: 2011-02-01 to: 2011-02-07

These are the final results of the Public Review Ballot for JSR #321. The Executive Committee for SE/EE has approved this ballot.

Votes

SE/EE

Credit Suisse

Eclipse Foundation, Inc

Ericsson AB

Fujitsu Limited

Google Inc.

Hewlett-Packard

IBM

Intel Corp.

Keil, Werner

Oracle

Red Hat

SAP SE

VMware

Icon Legend
Yes
No
Abstain
Not voted

View Vote Log

SE/EE

On 2011-02-02 SAP SE voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-03 Ericsson AB voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-04 Keil, Werner voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-04 IBM voted No with the following comment:
The current API is undesirably restrictive as it is limited to using SHA-1 digests and RSA keys: SHA-1 digests are already deprecated and will not be usable beyond 2013, whilst focus is moving from using RSA keys to Elliptic Curve Cryptography. 
Also, the APIs currently take passwords as String objects, which data, being immutable, linger in memory (at least) until they are GC'd. Best practice would be to use char arrays, where the data can be zeroed after use.
Due to these API flaws, IBM is not able to support the proposed spec at this point.
IBM's vote is based on the technical merits of this JSR and is not a vote on the licensing terms. IBM supports licensing models that create an open and level playing field by allowing third parties to create independent implementations of Java Specifications and that do not allow individuals or companies to exercise unnecessary control for proprietary advantage. We support open source as a licensing model for contributions in the JCP, and would hope others will support this direction. This comment is not necessarily directed at the current business or license terms for this JSR, however, it is a statement of IBM's preferred licensing model.
------------------------------------------------------------------------------
On 2011-02-04 Credit Suisse voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-07 Intel Corp. voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-02 Red Hat voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-03 Oracle voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-07 Hewlett-Packard voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-07 Eclipse Foundation, Inc voted Yes with no comment.
------------------------------------------------------------------------------
On 2011-02-07 Fujitsu Limited voted Yes with the following comment:
As IBM stated, SHA-1 digests are already deprecated. The API specification should describe how to handle this issue.


------------------------------------------------------------------------------