via RT wrote:
> Oops, overlooked the -debug option that prints the "Shared ciphers".
>
> Although, if that < ciphers:DHE-RSA-AES256-SHA:DHE-DSS-AES256-SHA:AES256-SHA:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA:RC4-MD5:RC4-SHA:AE
> S128-SHA:EDH-RSA-DES-CBC3-SHA:EDH-DSS-DES-CBC3-SHA:DES-CBC3-SHA:EDH-RS
via RT wrote:
Oops, overlooked the -debug option that prints the "Shared ciphers".
Although, if that <>
really is what firefox offers, why does it fail on EXPORT?
After all, e.g. EXP1024-RC4-SHA appears to be in common with
"openssl ciphers EXPORT"?
which openssl version do you use ? I remem
hi all,
let's try this again ...
i'm building on OSX 10.4.2.
i've upgraded OpenSSL from v0.9.7 --> v0.9.8, built into /usr/local.
when i build an app against ssl libs, e.g., here: 'lynx' (results are the same
for an/all other apps ...), 'otool -L' on the resultant binary shows:
FOR OPENSSL
Nils Larsch wrote:
OpenSSL CVS Repository
http://cvs.openssl.org/
Server: cvs.openssl.org Name: Nils Larsch
Root: /v/openssl/cvs Email: [EMAIL PROTECTED]
Module: opens
should be fixed, please test a recent snapshot
Thanks,
Nils
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Oops, overlooked the -debug option that prints the "Shared ciphers".
Although, if that <>
really is what firefox offers, why does it fail on EXPORT?
After all, e.g. EXP1024-RC4-SHA appears to be in common with
"openssl ciphers EXPORT"?
If a client and s_server cannot agree on a cipher, openssl only prints
<>
to stdout.
It would be great if, given an optional list-client-ciphers parameter
were provided on the command-line, it printed the cipher proposals
received by the client to stdout.
see https://bugzilla.mozilla.org/show
openssl is a great tool to determine whether a server is misconfigured
does an unintentional downgrade to weak ciphers.
e.g.
openssl s_client -connect pops.mydom.com:995 -cipher EXPORT
will either fail or find one.
However, it would be great to allow openssl diagnostically to discover
the
