4 ms·
CloudFlare Transparency Report on National Security Orders
- nacs 13y ago> Starting with 0-249 I'm puzzled why it's not 1-249 with 0 being a different group. So this law basically means that as long as you send less than 250 requests to a single company you're fine. Might as well start sending 249 requests to every company they can think of.
- deleted 13y ago[deleted]
- chimeracoder 13y ago> I'm puzzled why it's not 1-249 with 0 being a different group. So this law basically means that as long as you send less than 250 requests to a single company you're fine. I think you just answered your own question. The difference between 0 and 1 is pretty important. Think of it this way: until relatively recently, Github would return either a 500 or a login page (I forget which) if a logged-out user tried to access a private repo, whereas they would return a 404 if a logged-out user tried to access a nonexistent repo. If someone thought that you were working on a secret project and they had an idea what the project name might be, they would be able to confirm this with a simple HTTP request. They don't even need to see the contents of the repository in order to obtain what could be potentially damaging information (the mere existence of the project). This way, one can never be sure whether a company has received any letters, which is itself a rather valuable piece of information, until they have already received a large number (and presumably for a large number of targets).
- lstamour 13y agoCouldn't a service employ a warrant canary and effectively create a 0 bucket and a 0-249 bucket? I wonder... http://arstechnica.com/tech-policy/2013/11/apple-takes-strong-privacy-stance-in-new-report-publishes-rare-warrant-canary/ http://arstechnica.com/tech-policy/2013/11/apple-takes-stron...
- gojomo 13y agoMost likely neither the DoJ/DNI, nor any company that has received more than one request, wants a distinction that makes the first request stand out.
- benologist 13y agoThe cynic in me thinks the publicity associated with reporting anything is going to make it impossible to tell who got any at all once it's a marketing tool.
- dmn757 13y agoThe usage of a 0-249 block also keeps that sense of fear for the user base of the service(s). A sort of government scare tactic, you could say. If a service was allowed to say that they had 0 requests, perhaps more users would flock to that service as a less surveilled alternative to a competitor that is in the 1-249 bracket(or higher).
- deleted 13y ago[deleted]
- chimeracoder 13y agoAs a Cloudflare customer, I'm really happy to see this. Cloudflare provides a great service, but to do so, they have to assume a position of enough power that makes them an easy (legal) target for a determined government. As a US resident (and citizen), though, I find this very disconcerting. The difference between 0 and 249 requests is a lot. There isn't much else a company the size of Cloudflare can be expected to do (lobbying the government requires levels of cash that I doubt Cloudflare has right now), but it makes me sad that this is even newsworthy.
- rtfeldman 13y agoIt says 0-249, but it means 1-249. If you've never received one, my understanding is that there's no law preventing you from saying "0", so why wouldn't you if it were true?
- adventured 13y agoThis is correct. If they haven't received any, they can legally say so, and it would seem to imply they have received one or more.
- tlrobinson 13y agoThey say they've received 0-249 NSLs, but they also said "CloudFlare will therefore challenge in court any NSLs we receive." While it's possible this statement doesn't apply retroactively, they seem to be implying they haven't received any NSLs.
- eastdakota 13y agoNo, applies retroactively. Any NSLs we've received we've fought. And we'll continue to do so.
- tlrobinson 13y agoThe only remaining question is, are you able to publicly disclose when you fight NSLs?