Bodo Moeller wrote:
>
> If they're still using the same buggy server as a couple of months
> ago, then
>
> openssl s_client -ssl2 -bugs -connect banking.wellsfargo.com:443
>
> should work. Look in the s_client source to see what exactly this does
> (it sets all the bug workaround options).
Hey,
Its seems that with an ssl2 connection, no -bugs is needed, a connect
to banking.wellsfargo.com:443 works just fine.
What I'm trying to do is get Crypt::SSLeay to support connections
to as many web servers as possible. Are there some web servers
where only by turning the bugs options does allow one to connect
SSL_CTX_set_options(ctx,SSL_OP_ALL|0);
is there any reason not to use all the SSL options ? Is
the setting known for causing conflicts with any web servers?
Now there is finally another problem... it seems that
some servers can only support an SSLv2 connection and
some only SSLv3... SSLv23 doesn't work for others.
So to connect to as many https web servers as possible,
one should first try an SSLv2 connection with bugs on,
and then an SSLv3 connection with bugs on.
Yes? Do I have this right? Seems like the first SSLv2 connection
attempt will cover 99% of the cases, where the SSLv3 is needed
for a minority of sites.
Thanks,
Joshua
______________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NODEWORKS - web link monitoring Long Beach, CA USA 1-562-432-2469
http://www.nodeworks.com http://www.chamas.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
