SSL allow beast option? about go-curl

[andelf]

in https://github.com/bagder/curl/blob/7fef4016def79e35ef6194e9a44ef90075f84348/src/tool_operate.c#L1308

  if(config->ssl_allow_beast)
          my_setopt(curl, CURLOPT_SSL_OPTIONS, (long)CURLSSLOPT_ALLOW_BEAST);

in curl.h

#define CURLOPT_SSLKEYPASSWD CURLOPT_KEYPASSWD

in curl.h

#define CURLSSLOPT_ALLOW_BEAST (1<<0)

so
maybe easy.Setopt(curl.OPT_KEYPASSWD, 1) works?

[andelf]

If it does works, please let me know. I'll add the missing symbols.

[ottob]

I'm not sure I understand. Would using easy.Setopt(curl.OPT_KEYPASSWD, 1) in my code enable ssl allow beast?

[andelf]

Yes. In curl command line tool, --ssl-allow-beast means that.
follow the #defines, it means easy.Setopt(curl.OPT_KEYPASSWD, 1) in go-curl

[ottob]

Are you sure?
OPT_KEYPASSWD // password for the SSL or SSH private key. string. I don't see how this has anything to do with the CURLOPT_SSL_OPTIONS that is set in curl when you enable allow beast.

[andelf]

Oh sorry, I made a mistake. just ignore what I said above.
I'll fix these missing options soon.

[andelf]

please update go-curl to newest and try:
easy.Setopt(curl.OPT_SSL_OPTIONS, curl.SSLOPT_ALLOW_BEAST)

[ottob]

I tried it and still cannot connect to the server (maybe ssl allow beast isn't the solution to my problem though).

Is there any way that I can verify that ssl allow beast is actually enabled? Verbose logging?

[andelf]

maybe your can try ssl allow beast option with curl command line tool, to see if it works.

[ottob]

I tried it now and it doesn't make any difference. So I guess the problem is elsewhere. Thanks for helping me out and adding the option though. Maybe somebody else will find it useful :)

[ottob]

With some more research it seems like I was bitten by this bug this.

So workaround for me was easy.Setopt(curl.OPT_SSLVERSION, 1)

[andelf]

:)