Debian Bug report logs - #704234
misleading debug message implies relaying via Google

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: submit@bugs.debian.org

Subject: sends call via Google

Date: Sat, 30 Mar 2013 01:59:08 +0100

Package: telepathy-gabble
Version: 0.16.5-1
Severity: important


Troubleshooting with this debug command:

G_MESSAGES_DEBUG=all GABBLE_PERSIST=1 GABBLE_DEBUG=all
/usr/lib/telepathy/telepathy-gabble -f

I noticed the following line:

(telepathy-gabble:9974): gabble-DEBUG: gabble_call_stream_constructed
(call-stream.c:353): Attempting to create Google relay session


it appears to suggest that calls are relayed through Google's server
(using TURN?), even though no Google accounts are defined in empathy.


This may be against the privacy expectations of many users.

Message #10 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: 704234@bugs.debian.org

Subject: upstream comments

Date: Sat, 30 Mar 2013 10:13:00 +0100

This post in the upstream discussion list seems to confirm what has been
observed[1], they are hardcoding Google server details into the call setup


It also suggests that there is a dependency on the Google
infrastructure, if Google changes it, then Empathy breaks.  This could
explain with Video/Audio calling is broken at present[2]




1. http://lists.freedesktop.org/archives/telepathy/2010-October/004998.html


2. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704232

Message #15 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: 704234@bugs.debian.org

Subject: Re: Bug#704234: sends call via Google

Date: Tue, 02 Apr 2013 15:25:17 +0100

retitle 704234 misleading debug message implies relaying via Google
severity 704234 minor
thanks

> (telepathy-gabble:9974): gabble-DEBUG: gabble_call_stream_constructed
> (call-stream.c:353): Attempting to create Google relay session
> 
> it appears to suggest that calls are relayed through Google's server
> (using TURN?), even though no Google accounts are defined in empathy.
> 
> This may be against the privacy expectations of many users.

The debug message is somewhat misleading. From the source code, this
debug message is emitted whenever a call is using Google's non-standard
ICE variant:

  if (transport == JINGLE_TRANSPORT_GOOGLE_P2P)
    {
      DEBUG ("Attempting to create Google relay session");

but on non-Google accounts, we don't "attempt" very hard: we notice that
we don't have a TURN server, and immediately give up. A few log messages
down you should see this debug message from Wocky (you might need to set
WOCKY_DEBUG=all to see it):

    DEBUG ("No relay server provided, not creating google relay session");

We prefer google-p2p over standard ICE for historical reasons, and
because for Google accounts, it offers the possibility of using Google's
TURN relays in situations where the call would normally fail altogether.
Using Google's TURN servers requires temporary credentials which they
only hand out to users of Google accounts. The practical result is that
we are able to use TURN if either the telepathy-gabble user, or the peer
with whom they are communicating, is on a Google account (if we are, we
have our own credentials, or if the peer is, they use theirs).

Because of the way ICE works, if TURN is available we'll always send a
small amount of data through the relay (to check that it's a valid
"candidate"), but we only send audio or video through the relay on
problematic networks where STUN, etc. have failed. A user's XMPP service
provider is technically able to intercept calls through that provider
regardless of whether we use TURN, so we're only using Google's TURN
relay in situations where Google could already intercept the call if
they wanted to.

    S

Message #24 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Daniel Pocock <daniel@pocock.com.au>, 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704234: upstream comments

Date: Tue, 02 Apr 2013 15:38:45 +0100

On 30/03/13 09:13, Daniel Pocock wrote:
> This post in the upstream discussion list seems to confirm what has been
> observed[1], they are hardcoding Google server details into the call setup

The details discussed in that email are only the case for Google
accounts (GMail, "Google Apps For Your Domain" or similar) - notice that
the user in the quoted XML is user@gmail.com, and is sending a request
"to themselves", which is processed on their behalf by their own "home"
server, in this case gmail.com. Ordinary XMPP servers don't support the
google:jingleinfo extension, so we don't use it.

Strictly speaking, if a third-party XMPP service advertised support for
Google's google:jingleinfo extension, I suppose they could send back
details of their own TURN servers in the same way, and a token which can
be used to open sessions on their TURN servers via the same HTTP
requests used for Google's TURN servers. I'm not aware of any server
that actually does this.

I don't think there's a standard way to do the equivalent of
google:jingleinfo yet: service location could just be DNS SRV or
something, but the harder part is exchanging credentials to ensure that
only authorized XMPP users can use the TURN server, because TURN is
bandwidth-expensive.

> It also suggests that there is a dependency on the Google
> infrastructure, if Google changes it, then Empathy breaks.

TURN servers are used when either the telepathy-gabble user or their
peer has a Google account, and even then, only when STUN fails to
establish a connection: on a "friendly" network like a typical domestic
NAT, they won't be needed. If Google change their API for TURN, Google
accounts will regress to behaving like non-Google accounts do now.

    S

Message #29 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Daniel Pocock <daniel@pocock.com.au>

Cc: 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704232: empathy broken during Debian freeze

Date: Tue, 02 Apr 2013 15:52:04 +0100

On 30/03/13 09:23, Daniel Pocock wrote:
> Now, [calls are] not working.  I've posted a bug report here:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704232
> with logs.

We'll need the telepathy-gabble debug log, probably including Wocky
messages too ("WOCKY_DEBUG=all" is complete, if rather verbose).

For best log clarity, please enable exactly one XMPP account - ideally a
disposable test account with only one contact - and temporarily disable
all the others.

The Wocky debug log could contain password-equivalent material, your
contact list, etc., so please either use a "disposable" account or
censor it appropriately (in particular, delete the SASL handshake that
happens when you connect, typically starting with something like
<sasl:auth mechanism='PLAIN'/> and ending with <sasl:success/>).

Thanks,
    S

Message #34 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Simon McVittie <smcv@debian.org>

Cc: 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704232: empathy broken during Debian freeze

Date: Tue, 02 Apr 2013 23:58:31 +0200

On 02/04/13 16:52, Simon McVittie wrote:
> On 30/03/13 09:23, Daniel Pocock wrote:
>> Now, [calls are] not working.  I've posted a bug report here:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704232
>> with logs.
> 
> We'll need the telepathy-gabble debug log, probably including Wocky
> messages too ("WOCKY_DEBUG=all" is complete, if rather verbose).
> 
> For best log clarity, please enable exactly one XMPP account - ideally a
> disposable test account with only one contact - and temporarily disable
> all the others.
> 
> The Wocky debug log could contain password-equivalent material, your
> contact list, etc., so please either use a "disposable" account or
> censor it appropriately (in particular, delete the SASL handshake that
> happens when you connect, typically starting with something like
> <sasl:auth mechanism='PLAIN'/> and ending with <sasl:success/>).

Thanks for this feedback, I am definitely going to do these tests, it
may be a couple of days before I send you results, but it will be done
thoroughly as you describe.

Message #39 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Simon McVittie <smcv@debian.org>

Cc: 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704232: empathy broken during Debian freeze

Date: Wed, 03 Apr 2013 22:26:49 +0200

[Message part 1 (text/plain, inline)]

On 02/04/13 16:52, Simon McVittie wrote:
> On 30/03/13 09:23, Daniel Pocock wrote:
>> Now, [calls are] not working.  I've posted a bug report here:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704232
>> with logs.
> 
> We'll need the telepathy-gabble debug log, probably including Wocky
> messages too ("WOCKY_DEBUG=all" is complete, if rather verbose).
> 
> For best log clarity, please enable exactly one XMPP account - ideally a
> disposable test account with only one contact - and temporarily disable
> all the others.
> 
> The Wocky debug log could contain password-equivalent material, your
> contact list, etc., so please either use a "disposable" account or
> censor it appropriately (in particular, delete the SASL handshake that
> happens when you connect, typically starting with something like
> <sasl:auth mechanism='PLAIN'/> and ending with <sasl:success/>).
> 


Ok, here are the logs.  These logs are from the host using the identity
danieltest@pocock.com.au set up in a fresh Linux account.

In the first logs (empathy.log and gabble.log), I was trying to call
from danieltest@pocock.com.au to daniel@pocock.com.au (another host).
The calling machine made ringback sounds and the webcam image appeared.
 The called machine displayed a popup, I clicked to answer with video.
The incoming call window appeared and then immediately went into the
disconnected state.

In the second logs (empathy2.log and gabble2.log), I was trying to call
from the other host, daniel@pocock.com.au to danieltest@pocock.com.  The
calling host immediately showed the window in the disconnected state.
The called host never showed any indication that somebody was trying to
call.

Both hosts are on the same subnet.  ejabberd is in a data center.


I filtered these through grep -v sasl

[empathy.log.cleaned (text/plain, attachment)]

[empathy2.log.cleaned (text/plain, attachment)]

[gabble.log.cleaned (text/plain, attachment)]

[gabble2.log.cleaned (text/plain, attachment)]

Message #44 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Simon McVittie <smcv@debian.org>

To: Daniel Pocock <daniel@pocock.com.au>

Cc: 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704232: empathy broken during Debian freeze

Date: Thu, 04 Apr 2013 10:58:57 +0100

On 03/04/13 21:26, Daniel Pocock wrote:
> In the first logs (empathy.log and gabble.log), I was trying to call
> from danieltest@pocock.com.au to daniel@pocock.com.au (another host).
> The calling machine made ringback sounds and the webcam image appeared.
>  The called machine displayed a popup, I clicked to answer with video.
> The incoming call window appeared and then immediately went into the
> disconnected state.

After acknowledging the initial flurry of messages from danieltest,
daniel appears to be removing the audio content, resulting in call
termination:

* iq xmlns='jabber:client' from='daniel@pocock.com.au/c36b5105'
to='danieltest@pocock.com.au/dd1ed5d7' type='set' id='262641397743'
    * jingle xmlns='urn:xmpp:jingle:1'
initiator='danieltest@pocock.com.au/dd1ed5d7' sid='330546837'
action='content-remove'
        * content name='audio' senders='both' creator='initiator'

I can't tell why from danieltest's logs.

> In the second logs (empathy2.log and gabble2.log), I was trying to call
> from the other host, daniel@pocock.com.au to danieltest@pocock.com.  The
> calling host immediately showed the window in the disconnected state.
> The called host never showed any indication that somebody was trying to
> call.

This log doesn't contain any indication that danieltest received an
incoming call at all, so something is going badly wrong on daniel's side.

Would it be possible to test this with a second "disposable" account as
the other peer, and capture the logs on both sides?

    S

Message #49 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Simon McVittie <smcv@debian.org>

Cc: 704234@bugs.debian.org

Subject: Re: [Pkg-telepathy-maintainers] Bug#704232: empathy broken during Debian freeze

Date: Fri, 05 Apr 2013 08:54:37 +0200

[Message part 1 (text/plain, inline)]

On 04/04/13 11:58, Simon McVittie wrote:
> On 03/04/13 21:26, Daniel Pocock wrote:
>> In the first logs (empathy.log and gabble.log), I was trying to call
>> from danieltest@pocock.com.au to daniel@pocock.com.au (another host).
>> The calling machine made ringback sounds and the webcam image appeared.
>>  The called machine displayed a popup, I clicked to answer with video.
>> The incoming call window appeared and then immediately went into the
>> disconnected state.
> 
> After acknowledging the initial flurry of messages from danieltest,
> daniel appears to be removing the audio content, resulting in call
> termination:
> 
> * iq xmlns='jabber:client' from='daniel@pocock.com.au/c36b5105'
> to='danieltest@pocock.com.au/dd1ed5d7' type='set' id='262641397743'
>     * jingle xmlns='urn:xmpp:jingle:1'
> initiator='danieltest@pocock.com.au/dd1ed5d7' sid='330546837'
> action='content-remove'
>         * content name='audio' senders='both' creator='initiator'
> 
> I can't tell why from danieltest's logs.
> 
>> In the second logs (empathy2.log and gabble2.log), I was trying to call
>> from the other host, daniel@pocock.com.au to danieltest@pocock.com.  The
>> calling host immediately showed the window in the disconnected state.
>> The called host never showed any indication that somebody was trying to
>> call.
> 
> This log doesn't contain any indication that danieltest received an
> incoming call at all, so something is going badly wrong on daniel's side.
> 
> Would it be possible to test this with a second "disposable" account as
> the other peer, and capture the logs on both sides?
> 


Ok, I attach logs from both sides now

This test was just a call from danieltest1 to danieltest2

As with the call from danieltest1 to daniel,
a) danieltest1 gets ringback
b) danieltest2 was notified
c) danieltest2 clicked to accept with video
d) danieltest2's call window appeared
e) both danieltest1 and danieltest2 saw the call state `Disconnected'
immediately after the call was accepted

I also notice that the webcam light remains illuminated on both hosts
even after the call is disconnected

[dt1-empathy.log.cleaned (text/plain, attachment)]

[dt1-gabble.log.cleaned (text/plain, attachment)]

[dt2-empathy.log.cleaned (text/plain, attachment)]

[dt2-gabble.log.cleaned (text/plain, attachment)]

Message #54 received at 704234@bugs.debian.org (full text, mbox, reply):

From: Daniel Pocock <daniel@pocock.com.au>

To: Simon McVittie <smcv@debian.org>

Cc: 704234@bugs.debian.org

Subject: empathy failing / follow up bug #704234

Date: Wed, 17 Apr 2013 17:39:11 +0200

Hi Simon,

I'm just wondering if you had time to look at the latest logs I
submitted and if you can see any clues

I don't mind doing more troubleshooting or running it under a gdb if you
can provide some suggestions what I should check

I'm quite keen to find out if this is just an isolated issue or if it
will impact all Empathy users on Debian 7.

Regards,

Daniel

Message #59 received at 704234@bugs.debian.org (full text, mbox, reply):

From: "USPS Priority" <russell.conklin@einodia.com>

To: 704234@bugs.debian.org

Subject: New status of your USPS delivery (code: 62243519497)

Date: Thu, 26 Jan 2017 04:47:05 +0100

[Message part 1 (text/plain, inline)]

Dear Customer,



Your parcel was successfully delivered January 25 to USPS Station, but our courier cound not contact you.



You can download the shipment label attached!



With many thanks,

Russell Conklin,

USPS Parcels Delivery Clerk.

[Undelivered-Parcel-ID-62243519497.zip (application/zip, attachment)]

Message #64 received at 704234@bugs.debian.org (full text, mbox, reply):

From: "USPS Station Management" <james.perkins@otticaocchialissimo.com>

To: 704234@bugs.debian.org

Subject: Please recheck your delivery address (USPS parcel 60090740731)

Date: Fri, 27 Jan 2017 09:25:04 +0000

[Message part 1 (text/plain, inline)]

Dear Customer,



This is to confirm that your item has been shipped at January 25.



Review the document that is attached to this e-mail!



All the best,

James Perkins,

USPS Senior Delivery Manager.

[Delivery-Receipt-60090740731.zip (application/zip, attachment)]

Message #69 received at 704234@bugs.debian.org (full text, mbox, reply):

From: watdannai@sg2plcpnl0145.prod.sin2.secureserver.net

To: 704234@bugs.debian.org

Subject: New notice to Appear in Court

Date: Sun, 12 Feb 2017 05:01:44 +0000

[Message part 1 (text/plain, inline)]

Dear Sir or Madam,

You have to appear in the Court on the February 16 for your case hearing.
You are kindly asked to prepare and bring the documents relating to the case to Court on the specified date.

We attached the Notice to this e-mail.

Sincerely,
 ,
Clerk of Court.

[Notice_0000496527.zip (application/zip, attachment)]

Message #74 received at 704234-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 500650-done@bugs.debian.org,588637-done@bugs.debian.org,614574-done@bugs.debian.org,621922-done@bugs.debian.org,639667-done@bugs.debian.org,658094-done@bugs.debian.org,675742-done@bugs.debian.org,704234-done@bugs.debian.org,722098-done@bugs.debian.org,812435-done@bugs.debian.org,873124-done@bugs.debian.org,955948-done@bugs.debian.org,

Cc: telepathy-gabble@packages.debian.org

Subject: Bug#938637: Removed package(s) from unstable

Date: Wed, 30 Nov 2022 18:11:10 +0000

Version: 0.18.4-4+rm

Dear submitter,

as the package telepathy-gabble has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938637

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.