-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brian,
On 9/15/12 2:59 PM, Brian Braun wrote:
> Where can I get the list of all available ciphers for Sun JVM 6
> update 35?
Using Java 6u35, run this code (apologies for any poor word wrapping).
Enjoy,
- -chris
import java.util.ArrayList;
import j
Thanks a lot for the tip Edward. I will research it. However, I would have
to stop using JSSE in Tomcat and start using APR. Maybe I should, I really
don't know if it is supposed to be better than JSSE but I will investigate.
On Sat, Sep 15, 2012 at 10:10 AM, Edward Bicker wrote:
> Yeah, but I t
Thanks a lot Dan. I will do. I just hope all internet visitors will still
be able to browse by site. Do you think they will? How important could the
CBC ciphers be?
On Sat, Sep 15, 2012 at 10:57 AM, Dan Chernoff wrote:
> Your only other real option is remove any CBC and diffehelmen ciphers from
Well, I'm using JVM1.6 Update 35 (the latest). I want the best encription I
can get, while at the same time I want it to be near to 100% compatible
with all my possible internet visitor's browsers, and also I want to pass
the PCI test that www.secritymetrics.com performs. I have humble
requirements
On 15/09/2012 19:59, Brian Braun wrote:
> Hi Mark,
>
> I was really interested in your advice. I'm glad you answered, thanks!
> I'm trying not the disable TLS1.0 because I did a site that is being uses
> by unknown people over the internet, and I don't one how many of them are
> using a browser th
Hi Mark,
I was really interested in your advice. I'm glad you answered, thanks!
I'm trying not the disable TLS1.0 because I did a site that is being uses
by unknown people over the internet, and I don't one how many of them are
using a browser that only works with TLS1.0.
Where can I get the list
Your only other real option is remove any CBC and diffehelmen ciphers from your
supported cipher list. This really only leaves you with RC4 ciphers.
Dan
On Sep 14, 2012, at 5:14 PM, Brian Braun wrote:
> Hi Dan,
>
> Thanks a lot for your response!
> Contacting them will not work. I have had fa
Yeah, but I thought OpenSSL had a patch for this that worked.
Read...#2635: 1/n-1 record splitting technique for CVE-2011-3389
-Original Message-
>From: Brian Braun
>Sent: Sep 14, 2012 11:12 PM
>To: Tomcat Users List
>Subject: Is there a REAL solution to the "BEAST attack" (CVE-2011-338
Good Morning Brian
from what Im seeing this is a Redhat Enterprise 4,5,6 bug which effects any of
the secure protocols such as sftp, scp and ssl and you would need to implement
the RH patch
dsiable TLS 1.0 and implement either TLS 1.1 or TLS 1.2 protocols in its place
disable applets
disable W
Brian Braun wrote:
>Hi,
>
>Is there a REAL solution to the "BEAST attack" (CVE-2011-3389) for
>Tomcat
>7.x?
>For more info about this attack:
>http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3389
>
>My toughts and questions, as far as I have investigated this issue:
>
>- Disabling the TL
10 matches
Mail list logo
