Signature.getAlogrithm return null in special case (original) (raw)

Brad Wetmore bradford.wetmore at oracle.com
Tue Jun 18 00:44:43 UTC 2013


On 6/17/2013 5:38 PM, Brad Wetmore wrote:

Pushed. Thanks for the contribution.

P.S. http://hg.openjdk.java.net/jdk8/tl/jdk/rev/116050227ee9

Brad

Brad

On 5/27/2013 12:11 PM, Brad Wetmore wrote: Hi Deven,

I just got back from a short break, hope to return back to this shortly. I tweaked your test a bit before I left, but the builds were failing (unrelated issue) so I couldn't check in. Still need to check the actual Signature code for a couple things, but I think it's ok. Brad

On 5/21/2013 2:07 AM, Deven You wrote: Hi Brad, Thanks for your reply, is there any progress on this problem? I see the last comments on JDK-8014620 is six days before. Thanks a lot! On 05/15/2013 08:28 AM, Brad Wetmore wrote: Offhand, this seems reasonable.

Since you are an OpenJDK author, I've filed: JDK-8014620: Signature.getAlogrithm return null in special case and stocked it with your patch. Thanks, Brad

On 5/13/2013 9:46 PM, Deven You wrote: Hi All, I find in a special case: If you create a SignatureSpi service through extending Signature rather than SignatureSpi, the returned signature instance will lose its algortithm name. Though the fix[1] is simple I think it's valuable. Could anyone take a look? [1] http://cr.openjdk.java.net/~youdwei/ojdk-809/webrev/ <http://cr.openjdk.java.net/%7Eyoudwei/ojdk-809/webrev/> Thanks a lot



More information about the security-dev mailing list