April 2012
I think the following conclusion is correct: Google built a network that is adaptable to the compute requirements of their business.” —
Compute Conundrum for Vendors « SIWDT
Bingo. It’s not about the network. It’s about getting the damn thing out of the way.
(via abnerg)The real lesson: Google as a medium for launching an attack against others
Then I realized: This is a technique that can be used to launch a denial of service attack against a website hosted on Amazon (or even elsewhere). The steps:
1. Gather a large number of URLs from the targeted website. Preferably big media files (jpg, pdf, etc)
2. Put these URLs in a Google feed, or just put them in a Google Spreadsheet
3. Put the feed into a Google service, or use the image(url) command in Google spreadsheet
4. Sit back and enjoy seeing Google launching a Slashdot-style denial of service attack against your target.
What I find fascinating in this setting is that Google becomes such a powerful weapon due to a series of perfectly legitimate design decisions. First, they separate completely their index from the URLs that they fetch for private purposes. Very clean and nice design. The problem? No caching. Second, Google is not doing lazy evaluation in the feeds but tries to pre-fetch them to be ready and fresh for the user. The problem? Google is launching its Feedfetcher crawlers again and again. Combine the two, and you have a very, very powerful tool that can generate untraceable denials of service attacks.
” —The Google attack: How I attacked myself using Google Spreadsheets and I ramped up a $1000 bandwidth bill | A Computer Scientist in a Business School
NYC Open Data Policy Hack Day Saturday, May 19, 2012 at 11:00 AM (ET) REGISTER HERE
NYC recently enacted Local Law 11 of 2012, which mandates citywide open data in machine-readable formats through a centralized, publicly accessible web site. The NYC Open Data portal was launched in…
It’s with some excitement I see that the ONF has publicly released the OF-CONFIG specification to precious little fanfare. The head-spinner (in a positive sense) for me is that it includes a nice little RFC 2119-style MUST statement making NETCONF mandatory:
[…] OF-CONFIG1.0 requires that devices supporting OF-CONFIG 1.0 MUST implement NETCONF protocol as the transport. This in turn implies as specified by NETCONF specification that OpenFlow Capable Switches supporting OF-CONFIG1.0 must implement SSH as a transport protocol
” —Capital Letters Galore as The ONF Extends their SDN to Embrace NETCONF and YANG « On Network Management—
Smart.
At Interop Las Vegas 2012, Dell will demonstrate new SDN-based solutions showcasing the ease with which customers can virtualize their infrastructures and enable multi-platform orchestration and multi-tenancy.
As part of this, Dell also announced interoperability with Big Switch Networks Open SDN ™ architecture. Big Switch Networks delivers cloud networking solutions based on open standards such as OpenFlow, providing customers more networking choices within the SDN ecosystem.
” —Dell Strengthens Virtual Network Architecture Portfolio to Help Customers Deliver Results Faster | Dell