libstrophe through 0.14.0 contains a stack-based buffer overflow vulnerability in SCRAM_Hi that allows malicious XMPP servers to overflow a 128-byte stack buffer by sending an oversized SCRAM salt. Attackers can send a server-first-message whose s= attribute decodes to more than 124 bytes, aborting the client or overwriting stack memory in …

Simple readline and libstrophe based CLI XMPP client. - dpc/xmppconsole

XMPP/Jabber components which use non-viral licenses, or which allow dynamic linking from. XMPP libraries| License| About| Framework ---|---|---|--- _`net-im/loudmouth`_| LGPL2.1+| extensible, lightweight; client library| C _`net-im/qxmpp`_| LGPL2.1+| client library| QT & C++ _`net-im/libstrophe`_| MIT| minimal, uses minimal XML parsing library| C _`net-im/libmesode`_| MIT| fork of libstrophe| C _`net-im/py-slixmpp`_| MIT| fork of sleekxmpp| Python XMPP Clients| License| Comment| Framework ---|---|---|--- _`net-im/xmpp-client`_| BSD 3Clause| has OTR support| Go _`net-im/jsxc`_| MIT| has: video calls, file transfers, encrypted communication| Browser based XMPP security| License| Comment| Framework ---|---|---|--- _`security/libomemo`_| MIT| XEP-0384 v0.3.0| C, SQLite optional _`security/libotr`_| LGPL2.1| obsolete protocol| _`security/libotr3`_| LGPL2.1| obsolete protocol| XMPP server| License| Comment| Framework ---|---|---|--- _`net-im/prosody`_| MIT| flexible, light| Lua _`net-im/openfire`_| Apache 2.0| security and performance focused| XMPP misc| License| Comment| Framework ---|---|---|--- _`net-im/biboumi`_| ZLIB| XMPP gateway to IRC| uses SQLite or PostgreSQL _`net-im/matterbridge`_| Apache 2.0| bridge to multiple protocols including hipchat which uses XMPP| Go _`net-im/telepathy-gabble`_| LGPL2.1+| Jabber connection manager| _`net-im/telepathy-salut`_| LGPL2.1+| Link-local connection manager| `net-im/telepathy-*`| LGPL2.1+| Telepathy framework, lets people know presence settings| QT _`textproc/iksemel`_| LGPL2.1| XML parser library| XML _`net-im/prosody-modules`_| MIT| module components for prosody server| _`net-im/jitsi-prosody-plugins`_| Apache 2.0| prosody plugins for Jitsi| _`net-im/p5-Net-Jabber`_| LGPL2.0+| Perl access from Jabber to IRC or other services| Perl _`net-im/p5-Net-XMPP`_| LGPL2.1| Perl access to XMPP| Perl A lot of other p5 Perl components are dual licensed between GPL1 and ART10, which ART10 is considered to not have clearly defined rules for linking. Pidgin/libpurple libraries are under GPL, and not under LGPL or to another non-viral license, which makes them complicated to link to. As for client end programs, GPL is fine to use. The importance is that the libraries and other components allow wider use of them through dynamic linking. LGPL, other file-based license, and permissive licenses allow that type of dynamic linking for client end programs to use. Prosody under MIT gives more freedom of use for the server. Thread omemo-for-xmpp-on-freebsd.90599

XMPP/Jabber components which use non-viral licenses, or which allow dynamic linking from. XMPP libraries| License| About| Framework ---|---|---|--- _`net-im/loudmouth`_| LGPL2.1+| extensible, lightweight; client library| C _`net-im/qxmpp`_| LGPL2.1+| client library| QT & C++ _`net-im/libstrophe`_| MIT| minimal, uses minimal XML parsing library| C _`net-im/libmesode`_| MIT| fork of libstrophe| C _`net-im/py-slixmpp`_| MIT| fork of sleekxmpp| Python XMPP Clients| License| Comment| Framework ---|---|---|--- _`net-im/xmpp-client`_| BSD 3Clause| has OTR support| Go _`net-im/jsxc`_| MIT| has: video calls, file transfers, encrypted communication| Browser based XMPP security| License| Comment| Framework ---|---|---|--- _`security/libomemo`_| MIT| XEP-0384 v0.3.0| C, SQLite optional _`security/libotr`_| LGPL2.1| obsolete protocol| _`security/libotr3`_| LGPL2.1| obsolete protocol| XMPP server| License| Comment| Framework ---|---|---|--- _`net-im/prosody`_| MIT| flexible, light| Lua _`net-im/openfire`_| Apache 2.0| security and performance focused| XMPP misc| License| Comment| Framework ---|---|---|--- _`net-im/biboumi`_| ZLIB| XMPP gateway to IRC| uses SQLite or PostgreSQL _`net-im/matterbridge`_| Apache 2.0| bridge to multiple protocols including hipchat which uses XMPP| Go _`net-im/telepathy-gabble`_| LGPL2.1+| Jabber connection manager| _`net-im/telepathy-salut`_| LGPL2.1+| Link-local connection manager| `net-im/telepathy-*`| LGPL2.1+| Telepathy framework, lets people know presence settings| QT _`textproc/iksemel`_| LGPL2.1| XML parser library| XML _`net-im/prosody-modules`_| MIT| module components for prosody server| _`net-im/jitsi-prosody-plugins`_| Apache 2.0| prosody plugins for Jitsi| _`net-im/p5-Net-Jabber`_| LGPL2.0+| Perl access from Jabber to IRC or other services| Perl _`net-im/p5-Net-XMPP`_| LGPL2.1| Perl access to XMPP| Perl A lot of other p5 Perl components are dual licensed between GPL1 and ART10, which ART10 is considered to not have clearly defined rules for linking. Pidgin libraries are under GPL, and not under LGPL or to another non-viral license, which makes them complicated to link to. As for client end programs, GPL is fine to use. The importance is that the libraries and other components allow wider use of them through dynamic linking. LGPL, other file-based license, and permissive licenses allow that type of dynamic linking for client end programs to use. Prosody under MIT gives more freedom of use for the server. Thread omemo-for-xmpp-on-freebsd.90599