Bug#908598: RFP: libmesode -- Library for writing XMPP clients - fork of libstrophe for extra TLS functionality

[Prescott <prescott@hidalgo-monroy.com>]

Package: wnpp
Severity: wishlist

* Package name    : libmesode
  Version         : 0.9.1-2017.03.23
  Upstream Author : https://github.com/boothj5/libmesode
* URL             : https://github.com/boothj5/libmesode
* License         : (GPLv3)
  Programming Lang: (C)
  Description     : Library for writing XMPP clients - fork of libstrophe for extra TLS functionality

Currently, the 'profanity' XMPP client is built against libstrophe,
which does work perfectly fine in practice. This build, however, will
not allow a user to connect to a server with a self-signed SSL
certificate, as libstrophe offers no way to manually verify and allow an
SSL certificate. This is a big issue for small personal servers who'd
rather not go through that hassle, or more importantly, for anyone
running their server as an onion service. Despite onion services not
requiring SSL due to the nature of Tor's encryption, nearly all XMPP
clients will refuse to connect to a server without SSL encryption, 
forcing to use a self-signed one (most CA authorities will not work with
a .onion domain).

Libmesode will allow clients to be built against it and will give an
option to manually allow self-signed certificates, an option already
available in the more popular XMPP clients (pidgin, gajim).