10 ms·
Don't trust me: I might be a spook
- anon1385 13y ago>We need an army of software developers on the look out for potential NSA back doors — to borrow a phrase, if you see something, say something. And if you can't see anything because you can't get the source code... well, who knows that they might hiding? Of course this rules out all 'cloud' software other than simple dumb data storage. RMS was right again[1]. [1] "Cloud computing is a trap, warns GNU founder Richard Stallman" http://www.theguardian.com/technology/2008/sep/29/cloud.computing.richard.stallman http://www.theguardian.com/technology/2008/sep/29/cloud.comp...
- cperciva 13y agoCloud software is fine as long as you don't need to trust it. I use Google Calendar, for example, because it's convenient and I really don't care if the NSA knows when my next dentist appointment is.
- eliasmacpherson 13y agoThey might care when everyone's birthdays are though.
- zrail 13y agoThat information is already in many, many places. In particular, if you have a passport or drivers license it's already available to the government.
- aestra 13y ago@derefr, my sister had a similar thing happen. In the public records department someone possibly mistook a 7 for a 1 and my sister's original birth certificate got issued with the wrong date and was filed wrong. When my parents called about the error, they issued a new one, but never requested the old one back. She has two official birth certificates with two different birth dates. I'm not sure which one the government believes is "correct" but she's been using her real birthday birth certificate on all documents (drivers license, passport...) since.
- girvo 13y agoI have a birth certificate with a different last name, as my Dad adopted me (natural father and mother, got married a year later, born with mum's name but now have dad's once I turned about 1.5yrs). I even am pretty certain I have a second birth certificate with mt dad's name, but I'm not certain. I also have my adoption papers, and I left the country I was born in when I was young (7 years). As far as the country I live in is concerned I'm my Father's last name, but have legitimate primary ID with my mother's pre marriage last name. Always wanted to get my spy on and build up a second identity with that. Of course that's highly illegal, so itw only ever been a fun thought exercise :)
- derefr 13y agoIn fact, practically, your birth date is only your birth date inasmuch as the government believes that that's the date it is. If a nurse in the pregnancy ward makes a typo, and that's what gets submitted to the government, then that's your birth date, and no arguing. (I say this from a position somewhere in-between: I was born in British Columbia, and my birth date is right on my birth certificate, but wrong on the public-health-plan card you also get issued at birth. I had a very strange time bootstrapping my first credit card...)
- maxerickson 13y agoI like the linguistic ambiguity here. Of course, you are talking about a legal birth date and how in practice that is what matters, but really, what the government thinks has no bearing on your actual birth date.
- alan_cx 13y agoNo, but the NSA might care about your movements, who you know, who you deal with, and so on. Remember that video that was posted of a Lawyer given a talk to law students about never speaking to policemen? Remember how innocent things can be completely twisted and used against you? Yeah, I'd worry about the NSA snooping in my calendar.
- ihsw 13y agoThis cannot be understated, especially when it's not just the NSA snooping -- it's the entirety of the US Government. The DEA and the IRS revelations about using NSA-sourced information are just the tip of the iceberg, and it should be clear and obvious that there are use-cases for this data in a variety of other areas. Unless the government puts explicit restrictions (not secret restrictions!) on how their resources (not just stored data!) can be used and actively punishes those using it improperly, then it should be assumed that all the resources at the NSA's disposal will be used for the convenience of the rest of the government.
- beachstartup 13y agothe sad truth of the matter is it's a cultural thing, not a technology thing. sharing your calendar can be twisted against you. not sharing your calendar can also be twisted against you ("you don't seem to be sharing your calendar like most of your fellow citizens, what are you hiding?") see: mccarthyism.
- alan_cx 13y agoYeah, indeed. I remember some thing posted here a while ago about about a prospective employer assuming something is wrong with a candidate with out a facebook profile for the prospective employer to snoop over prior to hiring. Perhaps we should exercise our little grey cells more. Granted for a busy sales man or something that's impractical, but Im sure we could generally commit more exclusively to memory.. I posted this before, but to repeat... I think the legacy here is that we move more and more as a matter of habit or routine to a more secure way of living. No, we cant ever fully insulate ourselves from the NSA, but I think more and more of us will commit less to the internet, choose HTTPS via automatic extensions, use more secure software as a default, self censor, and so on.
- anonymfus 13y agoIt's very convenient for NSA to know your next dentist appointment because they can search your home at that time. Or install/remove bugs. BTW it's a major trope in spy movies. Literally dentist appointment in "The Tall Blond Man with One Black Shoe" ("Le Grand Blond avec une chaussure noire").
- TsiCClawOfLight 13y agoDid you read "The silicon jungle"? You Should. Holds for all of you, btw.
- alan_cx 13y agoI never liked the "cloud" from the start. To me it was simply dumb terminals all over again, which had the potential to shift everything to a server which was not mine. Security was an issue, but also it meant being reliant on the connection and service being up and running. In my experience, web sites were down more often than my desk top. And that's just on a personal level. Why a business would do such a thing was even more beyond me. Personal or business owned clouds for limited scope use, fine. But handing all that control over to a 3rd parts, over the net, in a foreign country? I see the marketed advantages, useful as a throwaway extra, but over all? No way.
- davidw 13y ago> Why a business would do such a thing was even more beyond me. Mostly the same reason they rely on third party infrastructure like electricity and plumbing: economics.
- belorn 13y agoBoth electricity and plumbing has immense regulations, and historical perspective of being neutral and non-threatening to businesses. Cloud services has none of that, and can cut off service for any reason. Work on any competing services that "the company" dislike, or do anything disruptive to people in power, and instant see your future, your business, you speech be taken down to a 404 not found. Any logs, any files, any property at all confiscated. Even pure money is not safe from "indefinite suspension of the account". Maybe this is a lesson that if you ever want to legally produce a scam, steal, or do anything that normally would land you in jail, all you need to do is go into producing third-party digital infrastructure. There is basically nothing a cloud service can do that would lend the owners to go to jail except tax evasion.
- deleted 13y ago[deleted]
- saosebastiao 13y agoThe regulation has to do with the fact that plumbing and electricity are Natural Monopolies. If they were not Natural Monopolies, they would have competition (as Cloud providers do), which acts as a form of regulation.
- Zigurd 13y agoThere are a lot of places the "cloud" can be zero-knowledge for payloads in storage, email, and real time communications, but most services are not set up that way, and they would have to charge a subscription fee to replace their ad revenue. It is possible to make cloud services where trust is not needed. It remains to be seen if cloud services will have to change to remain in business.
- derefr 13y agoPeople say email can be zero-knowledge, but I'm not quite sure--ever since Gmail pushed us from organizing everything into folders, to one giant Archive + labels, I find server-side search to be an essential attribute of my email service. I don't want to pull my entire mail history down onto my phone just to find one message; even the index would be ridiculous.
- Fargren 13y agoBut the server-side could be a desktop computer at your house instead of Google's servers. Seems harder for the NSA to access
- navait 13y agoThat sounds like a lot of work. You have to set up the server, get a domain, update it, back it up etc; What do you get out of it? An email server. Google will give you all of that in a few seconds. Google's uptime is way better than what I could hope to get. When my laptop had water spilled on it, there was no need to worry about my thesis. I went to a lab and started working on it again 10 minutes later. No work lost. My own backup solutions would be far worse, and likley involve losing some work. When using these services, I have to ask myself, how much do I value my privacy? I think I get more from google's services than I lose. For me, and a lot of people, it's not worth the time to set up an email server, let alone maintain one.
- gyepi 13y agoYes, for some people, it's too much work. However, there are many for whom it would not be at all. I have always run my own servers both for personal and business use and I don't find it the least bit onerous. Honestly, I think it only seems like too much work until one learns more about it. Just like anything else, I suppose. I'm not trying to change your mind; not everyone is meant to run their own systems. But I certainly want to counter your discouragement against doing so.
- devx 13y agoI wonder if stuff like this could help, but it could be years away from deployment anyway (and that's if the companies are even willing to do it - so all the more reason to avoid current cloud services): http://www.theregister.co.uk/2013/09/10/boffins_propose_more_spookproof_crypto/ http://www.theregister.co.uk/2013/09/10/boffins_propose_more...
- pyre 13y ago> Of course this rules out all 'cloud' software other than simple dumb data storage. This is pretty much the conclusion that I've come to as well. Using cloud storage to keep thing in sync, but only doing decryption on the client. Even doing something like storing a SQLite database and encrypting all of the fields seems like it would be leaking information rather than just encrypting/syncing the entire database.
- alan_cx 13y ago"The only solution is to read source code and look for anything suspicious. Linus's Law states that "given enough eyeballs, all bugs are shallow": If enough people read source code, we will find the bugs — including any which the NSA was hoping to exploit in order to spy on us. " I understand the point about software, but what about hardware? If the NSA is corrupting software, then it must be corrupting chips too. How can chips be verified NSA spy free?
- privong 13y agoI understand the point about software, but what about hardware? If the NSA is corrupting software, then it must be corrupting chips too. How can chips be verified NSA spy free? In principle, an analagous "Linus's Law" exists for open-sourced hardware. So if you have the code/design for chips, that could be verified as well.
- solarexplorer 13y agoAnd how do you verify that the design was not modified before the chip went into production?
- Fargren 13y agoSimilarly, how do you know your compiler didn't add a backdoor to your software? Even if you compiled your own compiler, you don't know if the software you used for that is safe. Unless you trust your hardware and you bootstrapped your compiler, I don't think you can truly trust software.
- mbq 13y agoSome strong solvent and a microscope? =)
- sliverstorm 13y agoA regular microscope? Maybe if you want to manufacture in a twenty year old process. Visible light only goes down to ~400nm, so no matter the magnification your eyes will not be able to see minimum size features on anything made since 1994 (600nm) or so.
- parennoob 13y agoSadly, for most users (read: people who don't program, or read HN, and even those who do), "Read the code and find bugs in it" is probably an impractical defense, although it is the logically correct one from the cryptographic point of view. An easier way for most people (Read: People who have never heard of cryptography. People who think 'DES' is a Government agency. People who think of an actual python when they hear 'python'. People who think Perfect Forward Secrecy means no one sees your Mom's embarrassing email forwards. There are a lot of such people, probably far more of them than software developers who speak C.) is probably to lobby for change in the draconian laws that authorize and encourage this sort of spookery. It is not a perfect solution, but in the long run, will probably make things easier for the average person.
- Tyrannosaurs 13y agoWhen it comes to crypto most people who read HN aren't close to being qualified to read the code and spot issues. The things the NSA is doing isn't putting in "IF password = 'Joshua" then LetMeIn()", it's subtle flaws in random number generators. The reality is that open source may be our best defence but it's still a pretty poor defence because of the complexity of what's been compromised. The more I think about it the more I think the actual best thing you can do is to pick obscure technologies that were probably too small to warrant NSA attention.
- cperciva 13y agoI've dealt with a lot of bugs in FreeBSD, and most of them were found by non-security-experts. The people finding said bugs didn't necessarily know enough to be able to exploit the bugs, or even enough to be certain that there was a bug; but there were a lot of "this code looks weird" reports turning out to expose vulnerabilities. I don't think you need to be a security or cryptography expert to find vulnerabilities the NSA might try to exploit.
- Tyrannosaurs 13y agoWhile you're right that fewer issues means fewer potential exploits, all you're really doing is getting rid of weaknesses that should never have been there in the first place, but you're doing nothing to address the systematic undermining of encryption standards and hardware and software implementations of them. To use a metaphor, it's great that you're making sure your windows are shut but the locksmith may have sold you a deliberately weak front door lock.
- shin_lao 13y agoThe only solution is to read source code and look for anything suspicious. Linus's Law states that "given enough eyeballs, all bugs are shallow Well. It's probably easier to break into your home, put an eavesdropping device and get your keys. I think it's important to audit code but let's be realistic, you won't defeat an agency that has you on your radar because you use "open source software". And by the way, Linus Law doesn't make any sense, simply because some bugs cannot be seen just by looking at the source code and also because the bandwidth between eyeballs that don't belong to the same brain is extremely limited.
- cperciva 13y agoIt's probably easier to break into your home, put an eavesdropping device and get your keys. If they were only targeting one person, maybe. But getting a back door added to a piece of widely-used software is much easier than bugging the homes of everybody who uses that software.
- shin_lao 13y agoThe backdoor can be anywhere between the two computers (most likely at the extremities though). I agree with you in the sense that software should be made as secure as possible, my comment is just a remainder that one should be realistic about what level of security he can get. If you didn't audit the hardware your software is running on and your local isn't physically secure spending so much time on software auditing isn't very useful. You'd even have to thoroughly double check that the software you have it the one you expect, audit your compiler, audit your os and recompile everything you have. You know better than me that there is no such thing as absolute security, so you're secure relative to a menace. If you try to secure yourself against a 1st world intelligence agency, I say... "Good luck". ;)
- EdiX 13y ago> you won't defeat an agency that has you on your radar because you use "open source software". The point is not to create obstacles to criminal investigations but to thwart massive online private data collection.
- 13y ago
- linhat 13y agoI do not know where this op-ed piece was intended for, but I think you should have written it anyway, stating just this feeling of yours. There was/is/will be so much media frenzy about this, every article (even if you think you really had nothing useful to say, which you actually do), op-ed or not, that does not resolve to sensationalists headlines is just really helpful.
- cperciva 13y agoI seriously considered it -- I even started trying to write a "there's nothing new here, the NSA has always been spying on us" editorial -- but I just couldn't make it work.
- tylerkahn 13y agoI don't see what the NSA revelations have to do with this line of reasoning. How do we know you're not (and have not been) selling tarsnap data to a corporation or non-US intelligence agency? This has always been a possibility and it has roughly equal probability to you being an NSA agent even after the Snowden leaks.
- marcosdumay 13y agoI don't see how you don't see a relation. You assume he is, then you read the source of the client that is sending the data, and verify that it's not. You trust the code, not the person. That's the TLDR of the article.
- derefr 13y agoNote that anyone who can't read code has to trust the person. I guess they should be trusting a person who has read the code? What happens if you don't personally know any software developers?
- tedunangst 13y agoWhat happens if you don't know any civil engineers? Do you stop driving over bridges?
- jasomill 13y agoBridges don't secretly collapse. And an overt collapse due to a serious, government-mandated secret weakness in design or construction leading to the revelation that a large portion of a "free" country's transportation infrastructure suffered from similar secret weaknesses in the name of national security would be a scandal of government-shattering proportions.
- weaksauce 13y agoAlso, since there is no downloadable binary, you must compile the code yourself.
- minimax 13y ago"I also pay for bugs people find in Tarsnap, as well as scrypt, kivaloo, and spiped, right down to the level of typographical errors in comments." I think these bug bounties are interesting. Is there something like a market price for one of these bugs? I.e. are other people out there besides Colin willing to pay for bugs in the tarsnap client?
- TsiCClawOfLight 13y agoThere is a black market for Viruses, Trojans, and Data - why shouldn't there be one for bugs?
- shabble 13y agoI imagine there could be a similar reputation market along the lines of the write-my-college-paper services, in which you sell the bug to someone who can then take credit for it. Certainly I'm sure you could find some people who'd be prepared to pay for a valid Knuth error, although exactly how you'd advertise/seek those who have such things would risk wrecking the value of the thing you seek to acquire. Stepping up from that, there are clearly existing markets for exploits, and you might be able to sell potentially exploitable bugs in the same way.
- jheriko 13y agothank you. common sense ftw. someone who doesn't seem generally surprised that the NSA are involved in espionage of all things... :) "Despite all the above, it is still possible that I am working for the NSA, and you should not trust that I am not trying to steal your data." now if you can just get people to pay attention to issues that result in dead children and reduced quality of /real/ life to people instead of overhyped and questionable civil liberties violations... XD
- cs702 13y ago"If you can't see anything because you can't get the source code... well, who knows what they might be hiding?" Actually, it's worse than that. Even if you can review the source code, you STILL won't know for sure. As Ken Thompson put it three decades ago, "no amount of source-level verification or scrutiny will protect you from using untrusted code."[1] This is because the tools we all use to process or transform source code (e.g., already-compiled-to-binary compilers, assemblers, loaders, etc.) may already contain secret back-doors. Ditto for even lower-level tools like hardware microcode. While open-source software tools -- and open hardware too -- are much less likely to have secret back-doors embedded in them, there are no 100% guarantees. Ultimately we have little choice but to trust the people who create, package, and distribute all the software and hardware we use but didn't create ourselves from scratch. -- EDITS: Added last paragraph. Made minor edits to second paragraph so it more accurately conveys my thoughts. -- [1] http://cm.bell-labs.com/who/ken/trust.html http://cm.bell-labs.com/who/ken/trust.html
- cperciva 13y agoIt's not quite as bad as it sounds: I don't think even the NSA has people smart enough to insert code into a compiler which will add backdoors to software which didn't yet exist when the compiler was written. If you're paranoid, use software written in the past 5 years and compile it on a system running FreeBSD 4.1 off a CD which you've had in your closet for the past decade.
- bvttf 13y agoI knew I was keeping all those discs for a reason!
- AnIrishDuck 13y ago> I don't think even the NSA has people smart enough to insert code into a compiler which will add backdoors to software which didn't yet exist when the compiler was written. I doubt such a thing is possible given the current state of the art in program analysis. Even if it were possible, it's hard to imagine it being undetectable (e.g. it would probably cause massive slowdowns in compilation). > If you're paranoid, use software written in the past 5 years and compile it on a system running FreeBSD 4.1 off a CD which you've had in your closet for the past decade. If you have a trusted compiler, you can bootstrap any non-trusted one [1]. That said, I suspect implementing diverse double-compiling to build any nontrivial system would take significant work. 1. http://www.dwheeler.com/trusting-trust/ http://www.dwheeler.com/trusting-trust/
- lhnz 13y agoThe most damaging thing is that I literally have no idea what is safe now - even good actors might unwittingly have been backdoored at the hardware level. I'm taking all private communication completely off the internet to minimise my exposure - I do not have enough knowledge or experience to make decisions on cryptography, nor sufficient need to waste time on this.
- pyre 13y agoBut where you are taking them? SMS? Phone calls? Maybe a private mesh network setup through line-of-sight directed antennas?
- lhnz 13y agoFace-to-face is the only way. All emails or SMS or phone calls have to be just stuff like "Hey, how are you are doing? Do you wanna meet up and have a beer."
- jmccree 13y agoDo you remove the battery from your phone before talking in person? The NSA could very well listen in to your phone's mic/s. Your phone probably has a camera or two. Even if you have no phone, everyone around you likely does. If you live in an urban area, your entire walk to the bar is likely on camera, the bar has cameras, your cab ride home has cameras, the transit bus has multiple cameras, the transit station has cameras, if you live in a high rise it likely has cameras, in a suburb atleast one of your neighbors have cameras. Most all of these cameras are now connected to internet enabled DVRs with questionable at best security. This is reality now. Privacy seems to be on it's last legs.
- lhnz 13y agoAnd I am happen to live in the UK where we have CCTV. ...you are right, we have woken to a truly disturbing reality.
- parley 13y agoEvery time these issues come up for discussion, my mind always returns to some sort of imagined utopia where our software is much more modular, composable and compartmentalizable (grammar?) than todays "mainstream" platforms. It could enable several different things, like running systems where most modules have access to much less resources of different kinds, allowing less mischief (microkernels, hierarchical resource mgmt frameworks like GenodeOS, etc). Greater modularity would also mean that basic or common modules would need less changes, requiring new audits less regularly, thus decreasing that load on the community. Of course many vulnerabilities are the result of unexpected interactions between modules, but then a certain composition of certain modules could be audited and hopefully not require any changes for some time. Being a software engineer I'm not kidding myself with regards to the huge software engineering problems inherent in achieving that, and of course the open source community already performs a lot of code reuse. Many will argue that an argument for more reuse is an argument against fragmentation and thus an argument against experimenting and forking. I guess that's true, but I still feel that more could be split and shared while still experimenting on many other things. There will also always be politics, personalities and the will to reinvent wheels for many reasons, like self-education or implementation pet peeves. Also, different languages and/or runtimes/VMs and their differing suitability for different environments affect fragmentation greatly. We probably won't ever end up with a single "winner", no matter how much many C/C++/JS/Go/Rust/Haskell/ATS/theorem provers we go through, and for reasons (only some of which are mentioned above) we probably don't want to. Dreaming is nice, though.
- chubot 13y agoDefinitely. One thing I've noticed is that constant code churn causes a huge amount of instability in many software domains (cloud, desktop, phone). The problem is only getting worse and will continue to get worse as software runs more of our lives and the world. Apple is sending down updates all the time; Ubuntu is; Google is, etc. Nobody can keep track of what the hell they're running. It's a security nightmare. There are so many components to systems now -- and not all of them need to change all the time. What I imagine, and what you seem to be hinting it, is that we have to do is factor software into processes which vary by the amount of code churn. Instead of having 1000 modules being patched every week, have 500 modules which change every 5 years, 300 which change every year, ... and maybe 2 or 3 which change every day. This would let us maintain the pace of software innovation. Unix does this to some extent -- think about when you would have a REAL need to upgrade "grep"? Almost never. It's basically hardware at this point. Likewise, with the architecture of Chrome and the Quark browser yesterday on HN, you could just update the rendering engine, or the JS engine, which run in restricted processes. Browser kernel updates could be separate, and verified separately. Related paper I found interesting: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.180.6737 http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.180.... We are moving closer and closer to "ubiquitous computing", and I agree with that paper in that software upgrade has to be treated like a first class problem. Right now even the best vendors are too sloppy about upgrades and modularity. I am constantly being nagged for updates on every device, and at work I am constantly dealing with shifting sands underneath my code.
- genecavanaugh 13y agoI think everyone is overlooking a significant threat. If we have information that is shared, we know when it is changed. The NSA has data that is not necessarily shared, so if the top people decide to "do you in", such as Obama and Romney, they have only to "edit" the data - and you have no way of proving they didn't. Meanwhile, we know the FISC will accept whatever NSA gives them as the absolute truth.
- deadfece 13y agoI'm glad I kept reading past the product plug.
- qu4z-2 13y agoCome on, that was clearly on-topic.
- educating 13y ago> If the NSA can break 2048-bit RSA, it would be a Big Deal 2048-bit is nothing. Here's why: 1. A great mathematician can find shortcuts. Tons of great mathematicians working in parallel will find them faster. 2. A fast processor can eventually brute force a key. Millions of fast processors working in parallel will find it faster. You are talking about a well-known method with a determinate algorithm. May as well just hand them a cake, because they are going to eat that up. Why use encryption mechanisms they've trained us to believe in and use? And how could be beat them at a game where they hold all of the talent and power? The only answer is to have dark encryption methods that are not shared, and that change frequently, frequently enough so there is no group of mathematicians with millions of servers that could determine the constantly changing algorithms.
- qu4z-2 13y agoSo you're suggesting we should just frequently change almost-certainly-flawed algorithms, but rely on their obscurity for security? I feel like there's a term for this strategy, but I can't think what it is...
- mbq 13y agoIndeed: http://www.daemonology.net/blog/2011-01-18-tarsnap-critical-security-bug.html http://www.daemonology.net/blog/2011-01-18-tarsnap-critical-...