4 ms·
If it was indeed a DNS attack, Twitter is damn lucky it was just a defacement (assuming it was just a defacement). The attackers very easily could have phished
by tlrobinson 17y ago
If it was indeed a DNS attack, Twitter is damn lucky it was just a defacement (assuming it was just a defacement). The attackers very easily could have phished anyone who logged in on twitter.com without https.
Even worse, any Twitter client which used Basic Auth without SSL would silently be compromising people's passwords when they auto-refreshed.
- tlrobinson 17y agoOn second thought, http://blog.twitter.com/2009/12/dns-disruption.html http://blog.twitter.com/2009/12/dns-disruption.html says twitter.com was redirected, yet the API still worked. Since the API uses the twitter.com domain name, unless I'm missing something the only way that's possible is if the API was being man-in-the-middled. Something doesn't add up.
- timdorr 17y agoProbably cached DNS. A lot of providers extend the TTL, despite what you have it set at.
- randallsquared 17y agoA lot of providers extend the TTL, despite what you have it set at. ...which is very annoying when you're moving a business site. :/
- jrockway 17y agoIndeed. But the user's ISP is the problem, so technically you are not to blame.
- randallsquared 17y agoTechnically true, but it doesn't stop my client from being upset that their user claims my client's site is down. :)
- jrockway 17y agoIndeed. If your site is down because of the user's error, but they can still get to your competitor's site, then that's bad for you. It might not be your fault, but you still missed out on a potential sale. All I can say is that I am glad I do not make money from the availability of websites :)
- randallsquared 17y agoI'm glad that I don't (directly) any more, either. :)
- wendroid 17y agoon third thought http://apiwiki.twitter.com/Things-Every-Developer-Should-Kno.. http://apiwiki.twitter.com/Things-Every-Developer-Should-Kno.... Post a status update and get the resulting status back as JSON: curl -u username:password -d status="your message here" http://twitter.com/statuses/update.json http://twitter.com/statuses/update.json what it doesn't tell you is that it sends the pw in the clear (unless you count base64 as crypto!)
- oscardelben 17y agoFrom an user viewpoint, how would you protect from a similar attack?
- peterwwillis 17y agoUse SSL. Make sure the cert is valid. And hope nobody comes up with yet-another SSL vuln. edit And hope that they haven't gotten a new valid cert by hijacking mail for the domain, too. edit Or, hard-code the domains and IPs in your hosts file.
- est 17y agodns fail == ssl CA fail It's easy to obtain a free but legal CA if you have control of a DNS. Only very few users would notice the change via the hash. Even your browser's SSL detection wouldn't yell anything.
- peterwwillis 17y ago... which is something i hate about most browsers. why don't they cache the cert indefinitely and wave a big red flag any time it changes at all? the occasional false alarm due to renewal would be a fair cost for the gain of more notice to unauthorized changes.
- est 17y agoNormal Internet users know shit about SSL and stuff. Perhaps they would call the broadband company when saw that. I always think browsers should be developed in two versions and can be switched by one key, one like MSN Explorer, one for advanced geeks with a console.
- gaius 17y agoTrue story: the ISP I use was acquired by Tiscali and shortly afterwards their cert expired. I called them up to tell them and they told me to turn my anti-virus software off and try again.