RFR: 8253176: Signature.getParameters should specify that it can throw UnsupportedOperationException [v2]

Valerie Peng valeriep at openjdk.java.net
Thu May 5 22:08:05 UTC 2022


On Thu, 5 May 2022 22:03:16 GMT, Valerie Peng <valeriep at openjdk.org> wrote:

>> I think this sentence covers case B, "... or may contain additional default or random parameter
>> values used by the underlying signature implementation."
>
> Sean's comment on the other PR regarding Cipher.getParameters implies otherwise, i.e. `A few comments:
> 
>     I don't think this new text covers the case where the cipher is not initialized with any parameters, but the provider returns parameters. I tried to think of how to say that all in one sentence, but I think it is best to have two sentences covering each case, ex: "If this cipher was not initialized with parameters, the returned parameters may be null or may be ..." "If this cipher was initialized with parameters, the returned parameters may be the same or may be ..."`

He later agrees that two sentences are probably too lengthy, so we ended up exploring other wording choices.

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

PR: https://git.openjdk.java.net/jdk/pull/8396



More information about the security-dev mailing list