RFR: 8154015 Apply algorithm constraints to timestamped code

Sean Mullan sean.mullan at oracle.com
Thu Jun 30 19:00:27 UTC 2016

Just a few comments -


79     private Date pkixdate = null;
81     private Timestamp jarTimestamp = null;

These can be marked final I think.

150      * {@code AlgorithmConstraints}.


153      * path for JAR files from deploy.

Avoid using "from deploy".

s/JAR files from deploy/signed JAR files that are timestamped./

159         this(certPathDefaultConstraints, jarTimestamp.getTimestamp());

This will throw NPE if jarTimestamp is null.

177     public AlgorithmChecker(AlgorithmConstraints constraints, Date 
pkixdate) {

I think this should be private. You are only calling it within the 
class. Also, the javadoc ctor description needs to be updated a little. 
SunJSSE doesn't call this ctor AFAICT.


107                 this.params = ((PKIXTimestampParameters) 

Shouldn't this be:

this.params = (PKIXBuilderParameters) params;

201         Timestamp getTimestamp() {

Can you rename this to timestamp() to be consistent with rest of classes 
methods that return params.


44     // Timestamp of the JAR file from deploy

s/JAR file from deploy/signed JAR file/


Since Timestamp is a new supported parameter, can you update the javadoc 
of Validator.validate() to describe it?


- missing copyright and class description

   30     public PKIXBuilderParameters getPKIXBuilderParameters() {

Do you need this method? See above comment on line 107 of PKIX.java

   44     public void setTimestampTrustAnchors(Set<TrustAnchor> t)

Does anyone call this method? Can it be removed?


On 06/28/2016 05:17 PM, Anthony Scarpino wrote:
> Hi,
> I need a review of the below code.  It's a continuation of the previous
> certpath related changes.  Additional constraints checking on
> timestamped jars being checked by the deploy code
> http://cr.openjdk.java.net/~ascarpino/8154015/webrev.01/
> thanks
> Tony

More information about the security-dev mailing list