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 1OoCl8-0003Us-87 for garchives@archives.gentoo.org; Wed, 25 Aug 2010 09:59:06 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 470FAE07D2; Wed, 25 Aug 2010 09:58:56 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 22CB3E07D2 for ; Wed, 25 Aug 2010 09:58:56 +0000 (UTC) Received: by ywp4 with SMTP id 4so247584ywp.40 for ; Wed, 25 Aug 2010 02:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Zewb36hM+1AOfSLd9gAMoAv4cvZioIj6H7Wd67mKNbg=; b=Bn/P7nnWyR121H2YoIUOv6tBxvM2tnsUcJvo2uR2V2/IEeprWMcQxmSO88gVhWmL8h gGesSBM7yleG2iiTENccGusZ/107okcEMqeEDDI9B4aCHFPB0OM3MzlRSov3x2SWTWtO vbA0v9CkXW0A/rC5cCkgb+r09gzipVKT/jai0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=bGR+aXSfSHTurjdv0g5esPOqlDd1/mR5ECrKaIeDCKTPPkSHnwqms/j/ZtwrcVaFHO +jkHsNtkBVAcZQh1qj8bb9IFI2a9j53lks51eeKcOL0EZRRbil2mQD4nCYdYVgFuAjOg a8VobnSTsurX+Ui5Ft3nBdrcxwLJ5bt30YOoA= Received: by 10.101.160.21 with SMTP id m21mr8851126ano.217.1282730335825; Wed, 25 Aug 2010 02:58:55 -0700 (PDT) Received: from [192.168.1.2] (adsl-240-57-38.jan.bellsouth.net [74.240.57.38]) by mx.google.com with ESMTPS id c19sm1866089ana.22.2010.08.25.02.58.53 (version=SSLv3 cipher=RC4-MD5); Wed, 25 Aug 2010 02:58:54 -0700 (PDT) Message-ID: <4C74E95C.1040104@gmail.com> Date: Wed, 25 Aug 2010 04:58:52 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100801 Gentoo/2.0.6 SeaMonkey/2.0.6 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Yahoo and strange traffic. 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> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 2c7bf247-220a-4380-8c3a-7c15f2a63c34 X-Archives-Hash: f71266092e0fcb763e6ecd72c2747f2d Joshua Murphy wrote: > Well, glancing at the GET request it's making there, as well as the > API google points me to when I look it up... > > http://developer.yahoo.com/messenger/guide/ch03s02.html#d4e4628 > > You're right that it's after an image from their profile, but the > cause of the failure appears to be related to some sort of credentials > Yahoo wants the messenger to provide. You might poke Kopete's > bugtracker to see if they've a related bug on file already, and if > they don't, throw one their way. > > The API Yahoo appears to be using there (based on a response I got > back in poking lightly) is, or is based on, OAuth, which according to > this: > > http://oauth.net/core/1.0/#http_codes > > specifies that a request should give a 401 response (Authorization > Required vs Unauthorized is purely the choice of phrase used in the > program decoding the numerical code, i.e. wireshark in your example of > it there) in the following cases: > > HTTP 401 Unauthorized > * Invalid Consumer Key > * Invalid / expired Token > * Invalid signature > * Invalid / used nonce > > Yahoo, essentially, *does* give a "bugger off"!! with that response, > but Kopete simply takes it, considers it a brief instant, then decides > "Maybe the answer will change if I try again *now*!"... at which point > it proceeds to introduce its proverbial cranium to the proverbial > brick and mortar vertical surface one might term "the wall." > Repeatedly. > > I was sort of figuring that it was trying to get something and Yahoo wasn't liking it. At least now we know for sure. I went to bug.kde and searched but I didn't see anything. Of course, I'm not really sure what the heck to look for since I don't know what is failing, other than Kopete. Thanks. Dale :-) :-)