[2608] in BarnOwl Developers
BarnOwl Twitter support is temporarily broken because Twitter is dicks.
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Thu Sep 2 14:05:51 2010
From: Nelson Elhage <nelhage@nelhage.com>
To: barnowl-users@mit.edu
Date: Thu, 02 Sep 2010 14:05:46 -0400
--=-=-=
Twitter doesn't ... really support open source clients any more, because
their engineers don't understand security at all.
I'm going to attempt to figure out a way to let BarnOwl Twitter continue
working, but I don't have a good workaround right now.
- Nelson
--=-=-=
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <>
X-Original-To: nelhage
Delivered-To: nelhage@lunatique.mit.edu
Received: from localhost (localhost [127.0.0.1])
by lunatique.mit.edu (Postfix) with SMTP id 51469951FB
for <nelhage>; Thu, 2 Sep 2010 13:30:34 -0400 (EDT)
Received: from mailhub-dmz-2.mit.edu (MAILHUB-DMZ-2.MIT.EDU [18.7.62.37])
by lunatique.mit.edu (Postfix) with ESMTP id 2A8536569B
for <nelhage@lunatique.mit.edu>; Thu, 2 Sep 2010 13:30:33 -0400 (EDT)
Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU [18.9.25.13])
by mailhub-dmz-2.mit.edu (8.13.8/8.9.2) with ESMTP id o82HTs1Y032353
for <nelhage@MIT.EDU>; Thu, 2 Sep 2010 13:30:33 -0400
X-AuditID: 1209190d-b7b38ae000006976-77-4c7fdf411931
Received: from smtp.zendesk.com ( [67.219.156.38])
by dmz-mailsec-scanner-2.mit.edu (Symantec Brightmail Gateway) with SMTP id 2A.97.26998.14FDF7C4; Thu, 2 Sep 2010 13:30:42 -0400 (EDT)
Received: from [10.0.64.103] (helo=zendesk.com)
by smtp.zendesk.com with esmtp (Exim 4.69)
(envelope-from <notifications-support@twitter.zendesk.com>)
id 1OrDcN-00049g-3T
for nelhage@MIT.EDU; Thu, 02 Sep 2010 17:30:31 +0000
Date: Thu, 2 Sep 2010 17:30:24 +0000
From: Ekdromos <notifications-support@twitter.zendesk.com>
Reply-To: Twitter Support <support+id1170786@twitter.zendesk.com>
To: Nelson Elhage <nelhage@mit.edu>
Message-Id: <XJM0QQKW_4c7fdf30ecdac_22c4b2daaa4354768bf@zendesk.com>
Subject: #1170786 Twitter Support: update on "Notice of Twitter API Keys Posted Publicly"
X-Delivery-Context: event-id-395118821
X-Mailer: Zendesk Mailer
X-Custom-Ip-Tag: zendesk
Auto-Submitted: auto-generated
X-Brightmail-Tracker: AAAAAhXbqt0V3HPy
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Thu Sep 2 13:30:34 2010
X-DSPAM-Confidence: 0.8512
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 3,4c7fdf3a314111804284693
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="===-=-="
--===-=-=
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
## Please do not write below this line ##
#1170786 Twitter Support: update on "Notice of Twitter API Keys Posted Publicly"
----------------------------------------------
Ekdromos, Sep 02 10:30 am (PDT):
Hello,
It has recently come to our attention that an application registered to you, BarnOwl, has had its Consumer Secret and Key pair posted publicly online here: http://github.com/nelhage/barnowl-twitter/tree/1eafdfaa641575186dfaf8f9310b6105b08f8d92
If an application's keys are posted publicly, it allows for external parties to hijack the application's API access and interact with the API on behalf of every user who has authorized that application. This presents an enormous abuse risk, and as such we've reset your API keys and ask that in the future you ensure these are not posted publicly. Moreover we've been forced to revoke the xAuth access your application was given in order to protect the integrity of the accounts that had authorized the use of your application.
You can respond to this message by replying from the address this email was sent to. If you respond from a different forwarding address or email alias (i.e. username+alias@gmail.com) your email will not be seen by our support staff.
If you have a Twitter account associated with this email address, you can also update and review this ticket online by clicking the ticket link above.
Thanks,
Twitter API Policy
--------------------------------
This email is a service from Twitter Support
--===-=-=
Content-Type: text/html; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
<html><body>
<div style=3D"margin:0px auto;text-align:center;font-size:12px;color:#A2A2A=
2;padding-bottom:6px">
## Please do not write below this line ##
</div>
<table cellspacing=3D"0" cellpadding=3D"0" width=3D"100%">
<tr>
<td>
<table width=3D"100%">=20=20=20=20
<tr>
<td style=3D"font-size: 12px; font-weight: bold; color: #fff; line-=
height: 1.5em;font-family: Helvetica, Arial, sans-serif; width: 100%;text-a=
lign: center;background: #98c332; padding:8px; margin:4px">
<style>.zd_link {color:#FFF;}</style><a href=3D"http://twitter.zendes=
k.com/tickets/1170786" class=3D"zd_link">Ticket #1170786: Notice of Twitter=
API Keys Posted Publicly</a>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td style=3D"text-align:center;padding-left:4px">=20=20=20=20
<table width=3D"100%">
<tr>
<td style=3D"font-size: 12px; font-family: Arial;font-style:normal; f=
ont-variant:normal;padding:8px;text-align:left">
<p><hr style=3D'border: none 0; border-top: 1px dashed #C2C2C2;height:=
1px;margin:15px 0 0 0'/>
<strong>Ekdromos, Sep 02 10:30 am (PDT):</strong><p>Hello,</p><p>It has rec=
ently come to our attention that an application registered to you, BarnOwl,=
has had its Consumer Secret and Key pair posted publicly online here: <a h=
ref=3D"http://github.com/nelhage/barnowl-twitter/tree/1eafdfaa641575186dfaf=
8f9310b6105b08f8d92">http://github.com/nelhage/barnowl-twitter/tree/1eafdfa=
a641575186dfaf8f9310b6105b08f8d92</a></p><p>If an application's keys are po=
sted publicly, it allows for external parties to hijack the application's A=
PI access and interact with the API on behalf of every user who has authori=
zed that application. This presents an enormous abuse risk, and as such we'=
ve reset your API keys and ask that in the future you ensure these are not =
posted publicly. Moreover we've been forced to revoke the xAuth access you=
r application was given in order to protect the integrity of the accounts t=
hat had authorized the use of your application.</p><p>You can respond to th=
is message by replying from the address this email was sent to. If you resp=
ond from a different forwarding address or email alias (i.e. <a href=3D"mai=
lto:username+alias@gmail.com">username+alias@gmail.com</a>) your email will=
not be seen by our support staff.</p><p>If you have a Twitter account asso=
ciated with this email address, you can also update and review this ticket =
online by clicking the ticket link above.</p><p>Thanks,<br />Twitter API Po=
licy</p> </p>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td>
<table width=3D"100%">
<tr>
<td style=3D"font-size: 12px; font-weight: bold; color: #fff; line-=
height: 1.5em;font-family: Helvetica, Arial, sans-serif; width: 100%;text-a=
lign: center;background: #98c332; padding:8px">
This email is a service from Twitter Support
</td>
</tr>
</table>
</td>
</tr>
</table>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=09=09=20=20=
=20=20=20=20=20=20=20=20=20=20
</body></html>
--===-=-=--
--=-=-=--
