Andrew Cooke | Contents | Latest | RSS | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

Surprise Paradox; [Books] Good Author List; [Computing] Efficient queries with grouping in Postgres; [Computing] Automatic Wake (Linux); [Computing] AWS CDK Aspects in Go; [Bike] Adidas Gravel Shoes; [Computing, Horror] Biological Chips; [Books] Weird Lit Recs; [Covid] Extended SIR Models; [Art] York-based Printmaker; [Physics] Quantum Transitions are not Instantaneous; [Computing] AI and Drum Machines; [Computing] Probabilities, Stopping Times, Martingales; bpftrace Intro Article; [Computing] Starlab Systems - Linux Laptops; [Computing] Extended Berkeley Packet Filter; [Green] Mainspring Linear Generator; Better Approach; Rummikub Solver; Chilean Poetry; Felicitations - Empowerment Grant; [Bike] Fixing Spyre Brakes (That Need Constant Adjustment); [Computing, Music] Raspberry Pi Media (Audio) Streamer; [Computing] Amazing Hack To Embed DSL In Python; [Bike] Ruta Del Condor (El Alfalfal); [Bike] Estimating Power On Climbs; [Computing] Applying Azure B2C Authentication To Function Apps; [Bike] Gearing On The Back Of An Envelope; [Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life

© 2006-2017 Andrew Cooke (site) / post authors (content).

My Current Take On Surveillance Scandal

From: andrew cooke <andrew@...>

Date: Fri, 7 Jun 2013 18:28:21 -0400

The Verizon order requested "information on all calls" - basically, all
metadata (not voice records).
http://www.guardian.co.uk/world/2013/jun/06/nsa-phone-records-verizon-court-order

Denials from Google and Facebook are, presumably, worded very carefully to
present the best possible version while remaining "legally true".  They
admit to complying with "legal requests" but deny "direct access" (that
exact phrase is common to both below) or requests on the scale of the
Verizon order.
https://www.facebook.com/zuck/posts/10100828955847631
http://googleblog.blogspot.com/2013/06/what.html

But if the NSA only requries metadata then they don't need to demand direct
access from Facebook or Google.  It's sufficient to use the data from ISPs
(like Verizon).  In fact, it would be pointless - they would simply be
duplicating data.

Traffic analysis (which seems to be what Prism is) does not require the
cooperation of the companies that provide the endpoints.  Because of the way
the internet works, it's sufficient to take the information from the people
who connect the servers to the clients.

Now things may be complicated by big companies like Google owning their own
CDNs, but it's not clear to me that invalidates the general argument (the NSA
still know if someone is "connecting to Google", no matter which of Google's
endpoints they use).


After doing traffic analysis, the NSA will presumably want to investigate some
conversations in more depth.  And that will be done in a manner consistent
with the statements by Google, Facebook et al - legal, targetted requests.

This is consistent with the different historical attitudes from the two
industries.  Remember how AT&T bent over backwards to support monitoring,
while Google and Twitter have a good record of questioning and resisting
requests.

BUT it doesn't convincingly explain this
http://cdn.theatlantic.com/static/mt/assets/science/assets_c/2013/06/prism-slide-5-thumb-570x427-123899.jpg
(you'd have to argue that this diagram is simply showing when they started
making the legal requests; it seems to be claiming something more).

Andrew

Similar Analysis Here

From: andrew cooke <andrew@...>

Date: Fri, 7 Jun 2013 20:02:39 -0400

http://www.dailydot.com/news/how-prism-works-fisa-courts-nsa/

Andrew

Advertising Low Cost Routes?

From: andrew cooke <andrew@...>

Date: Fri, 7 Jun 2013 22:33:50 -0400

The suggestion here https://plus.google.com/+YonatanZunger/posts/huwQsphBron
(search for "suspicions") seems to be that NSA are advertising (and providing)
low cost routes for data. 

Credit https://news.ycombinator.com/item?id=5843380

Andrew

Obvious Question

From: andrew cooke <andrew@...>

Date: Fri, 7 Jun 2013 22:34:57 -0400

So when did Google introduce SSL?  And how much do we trust that?

Andrew

NYT Has More Details

From: andrew cooke <andrew@...>

Date: Fri, 7 Jun 2013 23:40:34 -0400

More details starting to emerge about how the companies co-operated to
streamline targetted requests (as suggested by the dailydot link above;
nothing to do with the low cost route idea).

http://www.nytimes.com/2013/06/08/technology/tech-companies-bristling-concede-to-government-surveillance-efforts.html?_r=0

Andrew

Comment on this post