Daniel Stenberg wrote:
> On Wed, 8 Feb 2012, Yang Tse wrote:
>
>>> CURLSSLOPT_ALLOW_BEAST
>>> --ssl-allow-beast
>>
>> +1
>>
>> 'enable' could be interpreted as if lib/curl itself initiated the BEAST
>> atack.
>
> Yes, I agree that "allow" sounds better than "enable". I'll rename the
> option and if no other objections pop up proceed and push it.
>
> Kamil: maybe you can just adapt your patch after my push and then push yours?

Or to make it uber clear:

CURLSSLOPT_ALLOW_VULNERABILITY_BEAST
--ssl-allow-vulnerability-beast

(If they want to do it, make 'em type!)

- Rich
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2012-02-08