Hi Brad,
Would you have time to review this trivial Ucrypto config file update?
It's related to the Solaris fix that you relayed to me.
Given that some of our test machines may still run pre-S11.3 releases
and that JDK 9 is already at Rampdown 1 phase, I updated the test to
ignore the exception
I see what you are saying.. It's a simple change that I can make on the
on my workspace.. I won't rev the webrev, but here is the change.
377 debug.println(key + ": " + e.getMessage());
Tony
On 01/31/2017 09:28 AM, Seán Coffey wrote:
Hi Tony,
Thanks for the update. I see y
Hi Tony,
Thanks for the update. I see your new webrev. I guess my point is that
if we're in verbose logging mode, then we should log the message from
the exception(.getMessage()) rather than the more (vague) "uses a
disabled algorithm" logged message.
I see the new code now iterating over th
