summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2011-03-23connection: use new wocky_porter_close_async behaviourcloseJonny Lamb1-50/+4
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-14start on 0.11.9Jonny Lamb2-2/+11
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-14version 0.11.8Jonny Lamb2-3/+3
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-14NEWS: updateJonny Lamb1-0/+3
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-14configure.ac: add a dummy --enable-gtk-doc flagJonny Lamb1-0/+6
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-14telepathy.am: update to latest version from tp-glibJonny Lamb1-1/+6
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-10Merge branch 'register-handler-from'Will Thompson13-44/+150
2011-03-10NEWS for Wocky updateWill Thompson1-0/+11
2011-03-10Update Wocky snapshot for wocky_porter_register_handler changesWill Thompson7-41/+24
2011-03-10mail-notification test: fix sender in new-mail pushWill Thompson1-2/+2
Previously, this test sent new mail notification stanzas from some random JID. <http://code.google.com/apis/talk/jep_extensions/gmail.html#notifications> clearly shows that the notifications come from the user's own JID. Gabble previously ignored the sender of these notifications, but will begin respecting them when we update our Wocky snapshot to make it straightforward to do so.
2011-03-10Roster: respond to malicious pushes we drop.Will Thompson4-2/+61
Gabble correctly does not process roster pushes from contacts other than our server. However, it does not send a reply back to the IQ, which is in violation of XMPP Core. This patch allows the IQ to fall through to the “no handler” code, which just sends back a generic IQ error. While we could craft a specific <forbidden/> error, I don't think it's necessary.
2011-03-10roster: test handling pushes without id='' attribute.Will Thompson3-1/+54
I previously believed that I had added code to WockyPorter such that, if someone sent us an IQ with no id='' attribute, it would be silently dropped rather than being handed up to the application. (This would technically be valid behaviour; RFC3920 §9.2.3 “IQ Semantics” says that “The 'id' attribute is REQUIRED for IQ stanzas.” <http://xmpp.org/rfcs/rfc3920.html#stanzas-semantics-iq>) I mentioned this to Rob, who was horrified, because Gabble's roster code specifically handles roster pushes lacking an id='' attribute because this happens in the wild. I checked, and I had apparently imagined that I had made the above change to WockyPorter. This patch adds a regression test to check that Gabble correctly processes roster pushes without an id='' attribute, and doesn't crash in the process.
2011-03-10contact-info: don't clobber the per-process array of vcard fields depending ↵Jonny Lamb1-4/+5
on server type Previously, when setting the Overwritten_By_Nickname flag on the FN/NICKNAME VCard field it was done in the per-process array. As a result, if you signed on with a Gtalk account, FN will be fiven said flag. If you then sign on with a non-Google account, the FN field will already have this flag set so both FN and NICKNAME will have it set, which is wrong. This is never a problem the other way round because Gtalk doesn't support the NICKNAME VCard field. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-10contact-info: use g_boxed_free instead of g_ptr_array_freeJonny Lamb1-1/+1
For consistency. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-09vcard/supported-fields.py: test for Overwritten_By_Nickname flagJonny Lamb2-22/+24
Also, fix the name of the other contact info field flag which was clearly changed at some point before it became undrafted. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-09contact-info: set Overwritten_By_Nickname for FN/NICKNAME as appropriateJonny Lamb1-26/+37
The supported_fields pointer array is now no longer one per process because it depends on what kind of connection you're on, but it means we now always free the pointer array! Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-03-02add Message.MessageTypes as a immutable propertyGuillaume Desmottes2-0/+2
2011-02-28gitmodules: update submodule URLsJonny Lamb1-2/+2
They've moved to fdo now. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-25GabbleRoster: verify that the item is not NULL in _maybe_removeMarco Barisione1-0/+1
2011-02-25GabbleRosterItem: fix the use of an uninitialised variableMarco Barisione1-1/+1
2011-02-25GabbleRoster: fix a leak of a GPtrArray when getting a contact's groupsMarco Barisione1-1/+1
2011-02-18Start NEWS for 0.11.8telepathy-gabble-0.9.10Will Thompson1-0/+8
2011-02-18Merge branch 'go-forth-and-spam-no-more'Will Thompson3-116/+257
Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
2011-02-17server-tls-channel.py: don't use "with" as we depend only on Python 2.5Marco Barisione1-2/+8
2011-02-16Bump nano-version to 0.11.7.1Will Thompson1-1/+1
2011-02-16Version 0.11.7telepathy-gabble-0.11.7Will Thompson2-3/+3
2011-02-16NEWS for 0.11.7Will Thompson1-0/+10
2011-02-16Add commentary for jingleinfo spoofing regression testWill Thompson1-2/+7
2011-02-16Try spoofing a google:jingleinfo querySjoerd Simons1-3/+25
This is a regression test for the bug fixed in the previous commit.
2011-02-16Ignore google:jingleinfo pushes from contacts.Will Thompson1-0/+16
Previously, Gabble would erroneously process google:jingleinfo updates sent by anybody, rather than only paying attention to those sent by the user's server. This may theoretically allow an attacker to trick Gabble into relaying streamed media through a server of the attacker's choosing, enabling them to intercept, obstruct or modify the user's audio and video calls. This patch addresses this flaw, following the same pattern as the corresponding check in the roster code. Note that even without this flaw, no security guarantees on media in calls can be provided in the presence of malicious network admins or insecure networks: an attacker who can eavesdrop the network traffic still has the ability to intercept the content of the call, as the media is transmitted unencrypted. Fixes: <https://bugs.freedesktop.org/show_bug.cgi?id=34048> Signed-off-by: Will Thompson <will.thompson@collabora.co.uk> Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
2011-02-14NEWS for jabber:iq:versionWill Thompson1-0/+3
2011-02-14Merge branch 'version'Will Thompson6-105/+125
Fixes: <https://bugs.freedesktop.org//show_bug.cgi?id=11291> Signed-off-by: Will Thompson <will.thompson@collabora.co.uk>
2011-02-14Add a test for jabber:iq:versionWill Thompson3-0/+39
2011-02-14connection: add support for jabber:iq:version (XEP-0092)Robert McQueen3-0/+31
Updates a patch from #11291, thanks to Michael Scherer <misc@mandriva.org> for the original patch.
2011-02-14connection: port IQ callbacks to WockyRobert McQueen1-106/+56
2011-02-14gabble: remove old caps caches now that they're in WockyJonny Lamb1-0/+20
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-08lib/ext/: install and uninstall both wocky *and* tp-yell where appropriateJonny Lamb1-0/+2
This was broken in 4d0d2af917188b. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-07plugins: stop talking about top_gabbledir, whatever that isJonny Lamb1-1/+1
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-07test-location: add fixmes for cache invalidation.Will Thompson1-0/+4
These have occurred to me … I don't think they're that important, but I thought it worth writing them down.
2011-02-07Location: implement RequestLocation.Will Thompson2-3/+147
2011-02-06Map WockyXmppConnectionError to TpError.Will Thompson1-0/+23
WockyPepService throws this back at me when I get disconnected while requesting the items for a node.
2011-02-06Location: make update_location_from_msg take a handleWill Thompson1-5/+4
This is basically symmetrical, but will make handling explicit PEP queries to our own JID work more reliably when that's readded next.
2011-02-06Location: better document location dictionary refcountingWill Thompson1-0/+8
2011-02-06Location: don't poll for people's locations.Will Thompson2-87/+47
As discussed on <https://bugs.freedesktop.org/show_bug.cgi?id=27693>, the point of PEP is that you never have to poll for people's latest location if you advertise the relevant +notify capability. So we shouldn't do this in response to calls to GetLocations() or GetContactAttributes(). Fixing <https://bugs.freedesktop.org/show_bug.cgi?id=31218> will essentially re-add this code...
2011-02-06Location: simplify contact attribute implementation.Will Thompson2-16/+9
The specification says that the attribute should be “omitted from the result if the contact's location is not known.” But previously Gabble would fill in an empty dictionary in this case. Correcting this simplifies the refcounting on the hash table, which wasn't obviously right before.
2011-02-06Location: simplify contact attribute test caseWill Thompson1-9/+19
A blanket assertion on the entire dictionary of dictionaries is much less useful than a succession of increasingly-specific assertions using our wrappers which print the arguments on failure.
2011-02-06Merge branch 'caps'Jonny Lamb2-5/+6
2011-02-06tube-caps.py: everyone has text capsJonny Lamb1-4/+5
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-06offline.py: don't let gabbletest connect for usJonny Lamb1-1/+1
Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
2011-02-03Merge branch 'file-uri-33471'Guillaume Desmottes7-65/+26
generated by cgit v1.2.3 (git 2.39.1) at 2025-03-14 11:57:50 +0000