changeset 23365:576528012cce

Don't impose a restriction on who you can send files to for XMPP. This allows file transfers to arbitrary chat users (if you know their JID and they know yours). File transfers in chats where you don't know the real JID will fail because the SOCKS5 DST.ADDR hash will not match on both clients (I can't see a way around this issue right now).
author Daniel Atallah <daniel.atallah@gmail.com>
date Sat, 14 Jun 2008 01:09:29 +0000
parents 30b5f145a0f7
children 05802d915c13
files libpurple/protocols/jabber/si.c
diffstat 1 files changed, 1 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/libpurple/protocols/jabber/si.c	Sat Jun 14 00:59:35 2008 +0000
+++ b/libpurple/protocols/jabber/si.c	Sat Jun 14 01:09:29 2008 +0000
@@ -806,7 +806,7 @@
 
 			g_snprintf(port, sizeof(port), "%hu", portnum);
 
-			purple_debug_info("jabber", "jabber_si_xfer_bytestreams_listen_cb() will be looking at jsx %p: jsx->streamhosts %p and ft_proxy_list[%i] %p",
+			purple_debug_info("jabber", "jabber_si_xfer_bytestreams_listen_cb() will be looking at jsx %p: jsx->streamhosts %p and ft_proxy_list[%i] %p\n",
 							  jsx, jsx->streamhosts, i, ft_proxy_list[i]);
 			if(g_list_find_custom(jsx->streamhosts, ft_proxy_list[i], jabber_si_compare_jid) != NULL)
 				continue;
@@ -1213,9 +1213,6 @@
 
 	js = gc->proto_data;
 
-	if(!purple_find_buddy(gc->account, who) || !jabber_buddy_find(js, who, FALSE))
-		return;
-
 	xfer = jabber_si_new_xfer(gc, who);
 
 	if (file)