-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tim,
On 3/3/13 4:18 PM, Tim Whittington wrote:
On Tue, Feb 19, 2013 at 10:59 AM, Giuseppe Sacco
giuse...@eppesuigoccas.homedns.org wrote: [...]
I listed all providers here:
On Tue, Feb 19, 2013 at 10:59 AM, Giuseppe Sacco
giuse...@eppesuigoccas.homedns.org wrote:
[...]
I listed all providers here:
http://centrum.lixper.it/~giuseppe/ipad-tomcat-list-ciphers-no-bouncycastle.html
as you may see, a few of them are TLS_RSA and TLS_DHE:
*
Hi Cris,
Il giorno ven, 15/02/2013 alle 12.36 -0500, Christopher Schultz ha
scritto:
[...]
Allow legacy hello messages: true [snip] http-192.168.1.55-8443-1,
READ: SSLv3 Handshake, length = 75 *** ClientHello, SSLv3
RandomCookie: GMT: 1360933724 bytes = { 203, 86, 168, 88, 75, 77,
52,
Hi Martin,
Il giorno ven, 15/02/2013 alle 18.29 -0500, Martin Gainty ha scritto:
someone put cipherSuites patch on TC 7 Connector..
*IF you are implementing TC7 Connector with cipherSuites attribute support
and have not specified cipherSuites supported by your ppk keys*
then yes its
On 18.02.2013 22:59, Giuseppe Sacco wrote:
A side note: is it possibile to put tomcat behind a web server and make
the latter encrypt in SSL? This would imply that communication between
the web server and tomcat would be in clear, but how do I create the
connector proxy* information? I may
Il giorno gio, 14/02/2013 alle 11.38 -0500, Christopher Schultz ha
scritto:
[...]
Tomcat version is the one shipped with Debian, and uses jdk
1.6.0_u39 with jce unrestricted policy. I also added bouncy castle
jar in $JAVA_HOME/jre/lib/ext and added its provider in
Il giorno ven, 15/02/2013 alle 09.39 +0100, Giuseppe Sacco ha scritto:
[...]
Connector port=8443 protocol=HTTP/1.1 SSLEnabled=true
maxThreads=150 scheme=https secure=true clientAuth=false
sslProtocol=TLS proxyName=www.my-visible-name.tld
proxyPort=8443 address=192.168.1.55 /
Debugging the SSL handshake, I found that the problem is really about
ciphers because the handshake fails with exception
javax.net.ssl.SSLHandshakeException: no cipher suites in common
So, this is really something to be investigated in JSSE instead of
tomcat. I am sorry for noise in this list :-(
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/15/13 9:07 AM, Giuseppe Sacco wrote:
Debugging the SSL handshake, I found that the problem is really
about ciphers because the handshake fails with exception
javax.net.ssl.SSLHandshakeException: no cipher suites in common
So,
someone put cipherSuites patch on TC 7 Connector..
*IF you are implementing TC7 Connector with cipherSuites attribute support and
have not specified cipherSuites supported by your ppk keys*
then yes its tomcats fault
Otherwise its not..
Ciao,
Martin Gainty
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/13/13 4:47 PM, Giuseppe Sacco wrote:
I have an application deployed on tomcat 6.0.35 and linux/amd64
with a JSSE https connector. When I try to connect to this site
with default iPad browser, I always get an error message about
On Thu, Feb 14, 2013 at 11:38 AM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Giuseppe,
On 2/13/13 4:47 PM, Giuseppe Sacco wrote:
iPad does try a few times, changing the version number, but it
fails every time and eventually
Tomcat by default should accept all the enabled cipher suites in an
SSLSocket, unless it has been configured to do differently. That list is far
longer than either of the client lists supplied.
-Original Message-
From: Giuseppe Sacco [mailto:giuse...@eppesuigoccas.homedns.org]
Sent:
Hi all,
I have an application deployed on tomcat 6.0.35 and linux/amd64 with a
JSSE https connector. When I try to connect to this site with default
iPad browser, I always get an error message about the connection cannot
be established.
Tomcat version is the one shipped with Debian, and uses jdk
14 matches
Mail list logo
