Flutterby™! : NSA and the cloud

NSA and the cloud

2013-10-30 18:35:22.057043+01 by Dan Lyke 2 comments

"Two engineers with close ties to Google exploded in profanity when they saw the drawing. "I hope you publish this," one of them said."

washington Post article on this.

[ related topics: Photography broadband Archival Woodworking ]

comments in ascending chronological order (reverse):

#Comment Re: made: 2013-10-31 00:56:45.685144+01 by: Dan Lyke [edit history]

And because it ties in with the UTF8 testing I've been doing recently: RT Sexy Parker Higgins @xor

SSL Added and removed here! (͡� ͜ʖ ͡�)

Edit: Aaaargh! I thought I had this working! Damn it!

#Comment Re: made: 2013-10-31 01:53:11.31981+01 by: meuon [edit history]

I understand why most of what goes on behind the "GFE" is not encrypted, and that in most/all cases Google's use of SSL is to protect OTHER people than Google (and their friends) from access to data.. ie: during transport. That doesn't surprise me. I want to remind people of some basic things (slightly freshened up):

Don't say or store anything on a computer (device/smart phone/...) that you don't want on the front page of next hours news blog (Drudge Report, etc..)
Any IT professional should be capable of properly encrypted email as a minimum.
We should develop and use more tools for end-to-end encryption.

I'm trying to figure out how to deliver a bunch of very confidential and important network diagrams, systems configurations and passwords to a group of IT professionals that have issues with password protect .zip's (placebo level encryption... keeps most mail scanners from opening them).

I assume everything I send via email is public, and except for a few crazies like Dan, probably public shortly after I send it even when it is encrypted. Because they'll decrypt it and put it somewhere where it gets copied/scanned/snarfed/.. They guy in the department that could do encrypted email, isn't allowed the information.

Comment policy

We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.

Flutterby™ is a trademark claimed by

Dan Lyke

for the web publications at www.flutterby.com and www.flutterby.net.