[erlang-questions] Upgrading gen_tcp socket to ssl

Francesca Gangemi <>
Tue Dec 9 10:30:22 CET 2008


Ingela Anderton Andin wrote:
>
>> I'm using ssl-3.10 and I still see the same problem:
>> "cacertfile" is required even if {verify,0} is explicitly specified as 
>> option .
>>
>> As example
>>
>>  ssl:connect("zimbra.erlangsystems.com", 443, [{verify,0},{ssl_imp,new}]).
>> {error,{eoptions,{cacertfile,[]}}}
>>
>>  ssl:connect("zimbra.erlangsystems.com", 443, [{verify,0}]).             
>> {ok,{sslsocket,5,<0.1664.0>}}
>>
>>     
> Sorry that was our mistake we forgot to remove the restriction in the
> "option list handling" it will be removed for the next release.
>   
Ok, I'll wait :-)
>> Trying to upgrade a tcp socket I put as cacertfile the filename of a 
>> certificate I have on my machine and I've got the following error report
>>
>>  ssl:connect(#Port<0.3428>,[{certfile,"certs/mycert.pem"},
>>  {keyfile,"certs/mycert.key"},
>>  {cacertfile,"certs/vsign.pem"},
>>  {verify,0}, {ssl_imp, new}])
>>
>> =ERROR REPORT==== 4-Dec-2008::17:57:05 ===
>> SSL: hello: ./ssl_record.erl:291:Fatal error: record_overflow
>>
>>   
> Is it possible for you to provide us with more information so we can 
> repeat your
> senario?
>   
I'm sorry I can't reproduce it anymore, maybe I did something wrong.
Thanks for your support.

Kind regards
Francesca




More information about the erlang-questions mailing list