Bug 36195 - ejabberd cannot connect to ldap server via TLS
Summary: ejabberd cannot connect to ldap server via TLS
Status: CLOSED WORKSFORME
Alias: None
Product: Sisyphus
Classification: Development
Component: ejabberd (show other bugs)
Version: unstable
Hardware: all Linux
: P3 normal
Assignee: Anton Farygin
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks: 34231
  Show dependency tree
 
Reported: 2019-02-28 04:23 MSK by Vladimir D. Seleznev
Modified: 2019-03-12 14:17 MSK (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir D. Seleznev 2019-02-28 04:23:27 MSK
$ rpm -q --qf '%{EVR}\n' ejabberd                                                                                                                
18.12.1-alt1                                                                                                                                                  
$ rpm -q --qf '%{EVR}\n' erlang                                                                                                                  
1:21.2.4-alt3                                                                                                                                                 

$ tail -F /var/log/ejabberd/ejabberd.log
2019-02-28 01:15:45.952 [error] <0.557.0>@eldap:connect_bind:1073 LDAP connection to ldap.server:636 failed: TLS Alert: handshake failure                 
2019-02-28 01:15:45.955 [error] <0.558.0>@eldap:connect_bind:1073 LDAP connection to ldap.server:636 failed: TLS Alert: handshake failure                 
2019-02-28 01:15:45.955 [info] <0.590.0> TLS client: In state hello received SERVER ALERT: Fatal - Handshake Failure                                          

2019-02-28 01:15:46.453 [debug] <0.557.0>@eldap:connect_bind:1051 Connecting to LDAP server at ldap.server:636 with options [{packet,asn1},{active,true},{k
eepalive,true},binary]                                                                                                                                        
2019-02-28 01:15:46.456 [debug] <0.558.0>@eldap:connect_bind:1051 Connecting to LDAP server at ldap.server:636 with options [{packet,asn1},{active,true},{k
eepalive,true},binary]                                                                                                                                        
2019-02-28 01:15:46.461 [info] <0.596.0> TLS client: In state hello received SERVER ALERT: Fatal - Handshake Failure                                          

This can be related: https://stackoverflow.com/questions/52637744/why-do-i-get-an-error-with-my-code-in-erlang-21-but-not-in-erlang-20
Comment 1 Aleksei Nikiforov 2019-03-05 16:58:49 MSK
Можете проверить решает ли ejabberd версии 19.02-alt1 из тестового таска #223782 данную проблему?
Comment 2 Aleksei Nikiforov 2019-03-12 14:17:30 MSK
Задание отправлено в Сизиф.

Если проблема всё ещё воспроизводится с новой версией, прошу предоставить информацию, достаточную для воспроизведения проблемы, и переоткрыть баг.