From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OoGUT-0006sX-AO for garchives@archives.gentoo.org; Wed, 25 Aug 2010 13:58:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 28DB7E0828; Wed, 25 Aug 2010 13:57:21 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 0A760E0828 for ; Wed, 25 Aug 2010 13:57:20 +0000 (UTC) Received: by vws15 with SMTP id 15so719664vws.40 for ; Wed, 25 Aug 2010 06:57:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=pM7mydVEX6+A9YZiE3qwEZILWvkk+3HHDSaiBru5JD8=; b=n/NPR7SaudGubMOSYanA8Lq3MY+kYSelpjYtjAsBetQvQYuqnImX6RmcCbcuhrcZnw 9nvR8S6FmQpOA2s1dhuB3uvZMzpXT4ANBbRoeHTeE2UIT2TV8D7XACeovS8BcO9gHIgi 0VPDIrS/4C+QGoj8aTvpbsaZW0m103KcegWrA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ZLJs9glx/7cXywVZPb+8J9LkmXRElkAMtmDB96bvBNF45p4dnW1Vma34s/0oi3v0gb m5n5b6mXao8rTLdwgZwZgfI77lGKN19QloCB/n7MEi6cAyMEkDdQSCFucOZhOXclElPJ QTzK/j9l2QxiEVgITdw5EQSboxNnjBOjDCOLg= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.220.121.202 with SMTP id i10mr5274942vcr.87.1282744639776; Wed, 25 Aug 2010 06:57:19 -0700 (PDT) Received: by 10.220.11.80 with HTTP; Wed, 25 Aug 2010 06:57:19 -0700 (PDT) In-Reply-To: <497260.25873.qm@web51908.mail.re2.yahoo.com> References: <4C684F59.3040903@gmail.com> <201008152329.44195.alan.mckinnon@gmail.com> <4C69C1E4.9090309@gmail.com> <4C69E3CD.5070108@gmail.com> <4C6A224C.2030100@gmail.com> <4C6A633F.5070409@gmail.com> <306497.5595.qm@web51905.mail.re2.yahoo.com> <4C74819A.90904@gmail.com> <4C74E95C.1040104@gmail.com> <497260.25873.qm@web51908.mail.re2.yahoo.com> Date: Wed, 25 Aug 2010 09:57:19 -0400 Message-ID: Subject: Re: [gentoo-user] Yahoo and strange traffic. From: Joshua Murphy To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 18e4674d-5ba3-4dd0-9842-1d11f8eddae2 X-Archives-Hash: efff6c95d99367994a56ae1d69b3fd2f On Wed, Aug 25, 2010 at 9:21 AM, BRM wrote: > ----- Original Message ---- > >> Joshua Murphy wrote: >> > Well, glancing at the GET request it's making =C2=A0there, as well as = the >> > API google points me to when I look it =C2=A0up... >> > >> > =C2=A0http://developer.yahoo.com/messenger/guide/ch03s02.html#d4e4628 >> > >> > =C2=A0You're right that it's after an image from their profile, but th= e >> > cause =C2=A0of the failure appears to be related to some sort of crede= ntials >> > Yahoo =C2=A0wants the messenger to provide. You might poke Kopete's >> > bugtracker to =C2=A0see if they've a related bug on file already, and = if >> > they don't, throw =C2=A0one their way. >> > >> > The API Yahoo appears to be using there (based on =C2=A0a response I g= ot >> > back in poking lightly) is, or is based on, OAuth, =C2=A0which accordi= ng to >> > this: >> > >> > =C2=A0http://oauth.net/core/1.0/#http_codes >> > >> > specifies that a request =C2=A0should give a 401 response (Authorizati= on >> > Required vs Unauthorized is =C2=A0purely the choice of phrase used in = the >> > program decoding the numerical =C2=A0code, i.e. wireshark in your exam= ple of >> > it there) in the following =C2=A0cases: >> > >> > HTTP 401 Unauthorized >> > =C2=A0 =C2=A0* Invalid =C2=A0Consumer Key >> > =C2=A0 =C2=A0* Invalid / expired Token >> > =C2=A0 =C2=A0 * Invalid signature >> > =C2=A0 =C2=A0* Invalid / used nonce >> > >> > =C2=A0Yahoo, essentially, *does* give a "bugger off"!! with that respo= nse, >> > but =C2=A0Kopete simply takes it, considers it a brief instant, then d= ecides >> > =C2=A0"Maybe the answer will change if I try again *now*!"... at which= point >> > =C2=A0it proceeds to introduce its proverbial cranium to the proverbia= l >> > brick =C2=A0and mortar vertical surface one might term "the wall." >> > =C2=A0Repeatedly. >> > >> > >> >> I was sort of figuring that it =C2=A0was trying to get something and Yah= oo >> wasn't liking it. =C2=A0At least now =C2=A0we know for sure. >> >> I went to bug.kde and searched but I didn't see =C2=A0anything. =C2=A0Of= course, >> I'm not really sure what the heck to look for =C2=A0since I don't know w= hat is >> failing, other than =C2=A0Kopete. > > Best bet would probably be to check with the Kopete devs on IRC or mailin= g list > (kopete-devel). > > Ben Yep, but... just from a glance at their bug tracker and their commits list... they made quite a few changes to the Yahoo plugin's handling of avatars and such in January that're in 4.4... so their go-to answer on Yahoo avatar related issues seems to be "Try it on 4.4, then come back if it's still broken." So... to save a little time and effort when that answer's thrown around... might be best to test with that. I don't have QT or anything that depends on it on any of my boxes (the only box I actually have X on right now's my netbook, so adding's not even a feasable option) and my yahoo account went dead a few years ago, so I'm not much use for testing. --=20 Poison [BLX] Joshua M. Murphy