Re: [9] RFR: 8042967: Add variant of DSA Signature algorithms that do not ASN.1 encode the signature bytes

At 05:42 PM 1/26/2015, Sean Mullan wrote: >On 01/25/2015 11:15 PM, Michael StJohns wrote: >>Sorry - I missed this the first time around I think this may not >>be the right approach... >> >>I'm concerned with trying to overload ECDSA and DSA which have always >>had relationships with very speci

disabled SSL3 not reflected in "supported protocols"

Hello, with the Java 7u76 update the default security setting is, that SSL3 is banned. At first I thought, this would reflect in enabled and supported protocols, however the list of supported protocols still contain SSL3 and I can also enable SSL3 and this is reflected on the getEnabledProtocols(

Re: [9] RFR: 8042967: Add variant of DSA Signature algorithms that do not ASN.1 encode the signature bytes

I thought a bit more about this and I think you have a good point. If other new Signature algorithms are added that require parameters, then this design won't work, because setParameter is only supposed to be called once. For example, I can't do this: sig.setParameter(SignatureFormatParameter