[erlang-questions] SSL Errors with R16B

Aaron France aaron.l.france@REDACTED
Fri May 31 09:28:30 CEST 2013


Hi,

I'm using httpc, so I tried:     httpc:set_options([{socket, {verify,
verify_none}}]). and I still receive the same error.

That's correct? If not; let me know. Thanks!

Regards,
Aaron


On Fri, May 31, 2013 at 9:19 AM, Bogdan Andu <bog495@REDACTED> wrote:

> may be the ssl stack  changed a bit and some defaults parameters.
>
> you may try to pass the ssl option {verify, verify_none} to ssl:connect
> function and see what happens.
>
> Bogdan
>
>
> On Thu, May 30, 2013 at 10:17 PM, Aaron France <aaron.l.france@REDACTED>wrote:
>
>> Hi,
>>
>> But why is it working on R15B? Is the ssl code basically broken on R15B?
>>
>>
>> On Thu, May 30, 2013 at 9:12 PM, <bog495@REDACTED> wrote:
>>
>>> Hello,
>>>
>>> verify the output of the command:
>>>
>>> $ openssl s_client -connect region-b.geo-1.identity.hpcloudsvc.com:35357
>>> ogdan
>>> it seems that there is a certificate self signed.
>>>
>>> May be a solution is to disable certificate verification on peer and see
>>> what happens.
>>>
>>> Bogdan
>>>
>>>
>>> On Thursday, May 30, 2013 5:43:04 PM UTC+3, Aaron France wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'm trying to make HTTPS calls to an API.
>>>>
>>>> My stack trace is:
>>>>
>>>> SSL: certify: ssl_handshake.erl:263:Fatal error: certificate unknown
>>>> ** exception error: no match of right hand side value
>>>>                     {error,
>>>>                         {failed_connect,
>>>>                             [{to_address,
>>>>                                  {"region-b.geo-1.identity.**
>>>> hpcloudsvc.com <http://region-b.geo-1.identity.hpcloudsvc.com>
>>>> ",35357}},
>>>>                              {inet,[inet],{tls_alert,"**certificate
>>>> unknown"}}]}}
>>>>      in function  herp_identity:login/3 (src/herp_identity.erl, line 9)
>>>>
>>>> I've looked at some other issues which point it to being a regression
>>>> in R16B and I've reverted to R15 and the issue is non-existent.
>>>>
>>>> Any tips on getting around this or will it require a patch in R16B? The
>>>> bug is still evident in HEAD so possibly not enough data has been gathered
>>>> about it.
>>>>
>>>> Regards,
>>>> Aaron
>>>>
>>>
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130531/eb9259b3/attachment.htm>


More information about the erlang-questions mailing list