Upgrade sleekxmpp to 1.3.2

[fabaff]

1.3.2

• CVE-2017-5589+ Multiple XMPP Clients User Impersonation Vulnerability

Tested with the following configuration:

notify:
  - platform: xmpp
    name: jabber
    sender: sender@jabber.org
    password: !secret xmpp_password
    recipient: home@jabber.org

Message sent with "Call Service"

{"message": "The sun is {% if is_state('sun.sun', 'above_horizon') %}up{% else %}down{% endif %}!"}

[mention-bot]

@fabaff, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @rmkraus and @pvizeli to be potential reviewers.

[thundergreen]

I get those error with following config:

  - name: thorsten
    platform: xmpp
    sender: home-assistant@xmpp.home
    password: home-assistant
    recipient: thorsten@emevth.no-ip.biz
    tls: false

ERROR MEssage:

17-04-04 10:44:07 ERROR (event_thread_0) [sleekxmpp.features.feature_mechanisms.mechanisms] No appropriate login method.
17-04-04 10:45:05 ERROR (event_thread_0) [sleekxmpp.features.feature_mechanisms.mechanisms] No appropriate login method.
17-04-04 10:45:07 ERROR (event_thread_0) [sleekxmpp.features.feature_mechanisms.mechanisms] No appropriate login method.
17-04-04 10:45:08 ERROR (event_thread_0) [sleekxmpp.features.feature_mechanisms.mechanisms] No appropriate login method.
17-04-04 10:45:09 ERROR (event_thread_0) [sleekxmpp.features.feature_mechanisms.mechanisms] No appropriate login method.
17-04-04 10:45:12 ERROR (read_thread) [sleekxmpp.xmlstream.xmlstream] Can not read from closed socket.
17-04-04 10:45:12 ERROR (read_thread) [sleekxmpp.xmlstream.xmlstream] Can not read from closed socket.
17-04-04 10:45:13 ERROR (read_thread) [sleekxmpp.xmlstream.xmlstream] Can not read from closed socket.

But message are delivered.

I am running my own jabber server :)