Hey everyone,
I've just stumbled across this bug, because we're using some
not-packaged software that worked fine on jessie, and on stretch
fails to connect to our internal jabber server.
It basically does this:
my $connection = Net::Jabber::Client -> new( debugLevel => $jabberdebug );
Control: reassign -1 sendxmpp 1.23-1.1
Control: severity -1 important
Control: retitle -1 sendxmpp: sendxmpp can't send message with TLS/SSL without
passing -tls-ca-path
On Wed, 28 Jun 2017 00:09:12 +0200, Markus Gschwendt wrote:
> > > Maybe I miss something obvious, but IMHO the bug should 1/
On Tue, 2017-06-27 at 23:08 +0200, gregor herrmann wrote:
> On Tue, 27 Jun 2017 21:06:20 +0200, Salvatore Bonaccorso wrote:
>
...
> > Maybe I miss something obvious, but IMHO the bug should 1/ be
> > reassigned to sendxmpp itself. Then the question is if sendxmpp
> > should
> > be patches
On Tue, 27 Jun 2017 21:06:20 +0200, Salvatore Bonaccorso wrote:
> > So far we have:
> > - a bug against libnet-xmpp-perl which is (at least partially) the wrong
> > package; the change in Net::XMPP is that it starts to pass on the
> > empty path to the ssl certs from sendxmpp to XML::Stream
Hi Gregor,
On Sun, Jun 25, 2017 at 11:40:09PM +0200, gregor herrmann wrote:
> On Sun, 25 Jun 2017 14:52:54 -0300, Eriberto Mota wrote:
>
> > > Another question: you marked this bug as "affects: sendxmpp
> > > ejabberd". The former is obvious but why the latter? I don't think
> > > that ejabberd
Control: affects -1 - ejabberd
On Mon, 26 Jun 2017 22:53:32 +0200, Markus Gschwendt wrote:
> On Mon, 2017-06-26 at 19:23 +0200, gregor herrmann wrote:
> > On Mon, 26 Jun 2017 00:36:27 +0200, Markus Gschwendt wrote:
> > Could you please also tell us if my interpretation of your message re
> >
On Mon, 2017-06-26 at 19:23 +0200, gregor herrmann wrote:
> On Mon, 26 Jun 2017 00:36:27 +0200, Markus Gschwendt wrote:
>
> Could you please also tell us if my interpretation of your message re
> ejabberd from my last mail was correct?
yes. in my opinion ejabberd is not effected.
the cause of
On Mon, 26 Jun 2017 00:36:27 +0200, Markus Gschwendt wrote:
> > - the idea to make this all easier for users by setting a sane
> > default in either sendxmpp or libxml-stream-perl;
>
> +1
> I'd like to have the path to the certs as default.
> Maybe both packages should have a default value.
On Sun, 2017-06-25 at 23:40 +0200, gregor herrmann wrote:
> On Sun, 25 Jun 2017 14:52:54 -0300, Eriberto Mota wrote:
> ...
> - the idea to make this all easier for users by setting a sane
> default in either sendxmpp or libxml-stream-perl;
>
+1
I'd like to have the path to the certs as
On Sun, 25 Jun 2017 14:52:54 -0300, Eriberto Mota wrote:
> > Another question: you marked this bug as "affects: sendxmpp
> > ejabberd". The former is obvious but why the latter? I don't think
> > that ejabberd uses XML::Stream or Net::XMPP …
>
> This information was provided by Markus Gschwendt
2017-06-25 11:40 GMT-03:00 gregor herrmann :
> On Sat, 24 Jun 2017 16:00:27 -0300, Eriberto Mota wrote:
>
>> > Now I'm a bit confused: Which "both" of the 3 options mentioned above
>> > work?
>
>> Worked fine:
>>
>> [ x ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
>> [ x
On Sat, 24 Jun 2017 16:00:27 -0300, Eriberto Mota wrote:
> > Now I'm a bit confused: Which "both" of the 3 options mentioned above
> > work?
> Worked fine:
>
> [ x ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
> [ x ] change line 223 in /usr/share/perl5/XML/Stream.pm
>
> I didn't test
2017-06-24 15:23 GMT-03:00 gregor herrmann :
>> The both options work fine. Thanks a lot for your help.
>
> Thanks for testing!
>
> Now I'm a bit confused: Which "both" of the 3 options mentioned above
> work?
> [ ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
> [ ] change
On Sat, 24 Jun 2017 15:13:49 -0300, Eriberto Mota wrote:
> > Looks like the path to the SSL cert(s) is empty.
> > I gues either sendxmpp should set it, or XML::Stream should use a
> > sane default.
> >
> > For the latter see /usr/share/perl5/XML/Stream.pm:
> > 223
2017-06-23 21:14 GMT-03:00 gregor herrmann :
> On Sun, 05 Feb 2017 10:24:24 +0800, Tommy Wu wrote:
>
>> After upgrade to 1.05-1, sendxmpp program can't send message to googole
>> hangouts.
>>
>> XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
>> XMPP::Conn:
On Sun, 05 Feb 2017 10:24:24 +0800, Tommy Wu wrote:
> After upgrade to 1.05-1, sendxmpp program can't send message to googole
> hangouts.
>
> XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
> XMPP::Conn: xmppCallbackInit: start
> XMPP::Conn: SetCallBacks: tag(message)
Control: severity 854210 serious
The package is breaking other packages, as sendxmpp. It is reflecting
in Stretch too. I need sendxmpp to receive important event notices
from my network.
Cheers,
Eriberto
This problem exists now in the actual stable release: debian stretch.
I can confirm this.
Same problem with my ejabberd server (on debian testing).
Package: libnet-xmpp-perl
Version: 1.05-1
Severity: important
Dear Maintainer,
After upgrade to 1.05-1, sendxmpp program can't send message to googole
hangouts.
XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
XMPP::Conn: xmppCallbackInit: start
XMPP::Conn: SetCallBacks:
20 matches
Mail list logo