[asterisk-bugs] [JIRA] (ASTERISK-24712) xmpp starttls problemcauses connection spew

[Matthias Urlichs (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Urlichs updated ASTERISK-24712:
----------------------------------------

    Environment: Linux with not-quite-correctly-installed openSSL  (was: Linux with not-quite-corectly-installed openSSL)

> xmpp starttls problemcauses connection spew
> -------------------------------------------
>
>                 Key: ASTERISK-24712
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24712
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_xmpp
>    Affects Versions: 13.0.2, 13.1.0
>         Environment: Linux with not-quite-correctly-installed openSSL
>            Reporter: Matthias Urlichs
>
> Three issues here.
> (A) ERROR[27439]: res_xmpp.c:2556 in xmpp_client_requested_tls: TLS connection for client 'asterisk' cannot be established. OpenSSL initialization failed.
> … so what exactly is the problem with initializing OpenSSL? do we get an error code or anything?
> (B) Asterisk now immediately retries the connection attempt. Which is extremely anti-social. There should *always* be at least a linear, or even an exponential, back-off. This goes on indefinitely, except …
> (C) ERROR[27439]: res_xmpp.c:3334 in xmpp_action_hook: xmpp_action_hook was called without a packet. This happens because the connection is closed by the server (you're flooding it, after all). Again, there is no back-off here, Asterisk immediately retries. And retries. And retries. By the time somebody notices the problem, the server has banned our IP.



--
This message was sent by Atlassian JIRA
(v6.2#6252)