SSL Error: alert internal error

[Cantor, Scott]

On 10/24/13, 7:33 PM, "Christopher Peters" <cjpeters at uci.edu> wrote:
>
>As I understand it, weak encryption methods are the culprit here.
>Apparently, when you use Tomcat 6.0.x (or 5.5, I honestly don't know if
>this applies to 7), the JSSE connector on port 8443 (instead of the APR
>connector) and you don't specify which "ciphers"
> to use, the java implementation of SSL will fail.

curl is very liberal about things and it generally accepts anything
reasonable. I don't see why supporting weak ciphers (wisdom of that aside)
would preclude connections by stronger ones, so I don't know what the
issue is.

>  I don't know if it's a security limitation or a misuse of some cipher,

Me either.

> but in any case I followed the directions here:
>
>
>http://blog.techstacks.com/2008/09/securing-ssl-in-tomcat-part-two.html
>
>
>
>And specified a list of ciphers to use, and that cleared the problem up.
>I might yet switch to the APR connector now that I know where the problem
>lies and the APR connector is purported to be the better configuration to
>use, but in the meantime I have
> a working system.

Could you please add a link or note about that to the wiki page covering
Tomcat setup?

And if possible, would you mind filing a bug against the SP for this? I
just want to get back to it next year and see if I can reproduce it before
I do another release.

-- Scott