Rsync.net Warrant Canary
rsync.net
rsync.net
Still, I assume a skilled lawyer would be able to convince a judge that the net effect is that users effectively obtain information about rsync.net being served a warrant quite closely around some specific date, and thus the service broke the law anyway (assuming secret warrants are lawful in the first place).
My understanding is that most observers believe that the sign is legal.
"It originated at the start of the last century as drivers started to run foul of police speed traps in which officers used a stopwatch to calculate whether or not a car was going too fast. Even then it was illegal to warn motorists about speed traps, but the AA advised its members to stop if a patrolman failed to salute, and the driver would then be given information about "road conditions" ahead."
(the point being they are not actively making a change [taking the sign down] to indicate a "visit". Could make a difference)
Still I believe you are correct, by having a publicly stated policy about their planned inaction when served a secret warranty is effectively the same as making a public announcement. Ballsy, but kudos to them for making a statement about their privacy beliefs.
Frankly, this is the kind of thing a five-year-old would come up with. "Yo, warden, I just created a new religion that says I have to have steak and hookers every day! Respect my religious freedom!" The law isn't that brittle. It's hackable, but you have to respect judges' latitude and legal sense.
There are a variety of circumstances under which the warrant canary would not be published. A warrant being served might be one (it might not), but there are certainly others: policy change being the most obvious.
I don't think there is a good legal precedent in general for maintaining that someone's failure to speak (under whatever circumstances) violates a provision for secrecy. I think that would be a hard argument to make, given that, at most, the failure to publish would lead some people to suspect that some kind of warrant had been served for something, somewhere, sometime in the past week or so, that rsync might have. Vague, at best.
Then consider that they would come under speech restrictions through no fault of their own. It may be contrived, but they would be standing in a courtroom having committed no bad acts.
Would a judge order them to construct and publish a false statement? That's the question, but can you find case law that shows this ever having happened?
If not, then regardless of how contrived it is, it's still legally novel.
Being served a warrant would not necessarily involve fault, either, yet it would put them under speech restrictions -- restrictions against making true and public statements. So current law already accepts that people can be punished for making true and public statements without committing any other bad acts.
I don't think the judge would order them to publish a false statement. I think the judge would simply punish them for revealing the warrant and respond to their pleas of speech coercion by saying, "Hey, your fault, not mine, and you did it on purpose." I mean, they're intentionally committing themselves to either publishing a false statement or breaking the law. They've showed their willingness, indeed their intention, to do one or the other if served with a warrant. If they intended to break the law, then they can hardly argue their innocence. If they intended to publish a false statement, then they can hardly argue that the court coerced them to do so. And the fact that they already explained their cunning plan means they can't argue lack of foresight, either.
As for novelty, I wouldn't even trust a lawyer to know whether this is novel. People have been splitting legal hairs since long before Solomon. Putting the letter of the law in contradiction to the spirit of the law is hardly a novel concept; this is just one possibly novel example. It's probably discussed in the Talmud somewhere. "Ah yes, the famous story of Francois the builder, who owed his brother Juan thirty-five rubles and agreed to repay him by shearing his sheep on the fifteenth day following the next new moon, knowing full well that the fifteenth day following the next new moon was a sabbath day, on which sheep-shearing was forbidden."
All they need to do is buy themselves one day, and have a track record of not being late with the updates.
Will you support my use of X ?
Yes. If you are using X with an rsync.net filesystem, we will support and troubleshoot your use of it, regardless of how complex or esoteric that usage or application is. All such support will be handled by a real live Unix engineer, and will never be dealt with by a ticket system, autoresponder, or first level / junior "technician".
Really ?!
Yes. We are not just providing offsite filesystems, we are providing complete, end to end, personal customer support.
I can't even get that level of support ("real live Unix engineer") at my current workplace when things go pear-shaped.
It seems like they've got a pretty good idea about what things cost them and can scale by charging the right price for their business. I think they'll do fine.
I've heard this 'it doesn't scale' argument many times, and I think the source is that the sort of skills it takes to maintain support infrastructure of that quality are quite different from and rarely present in the same individual (or management of a company) as the skills required to scale out a product to the mass market.
Also, I don't believe the mass market doesn't really want a unix nerd on the level 1 support line. they want someone who speaks 'normal person.'
Large ISPs routinely get subpoena requests all the time (i.e. they have teams that do only that). I think rsync.net is setting themselves up for a lot of undesired press when they finally have to do it.
sure, but I don't think they are secret very often.
But it probably wouldn't work anyway. If a judge agrees that there is a need for a secret warrant, it's serious enough (aka national security) that the judge will tell you to continue doing business as usual, including posting your weekly canary.
There is no harm to you of posting an incorrect warrant canary and if that's the only objection you have, the judge will be happy to give you immunity on that point.
If you refuse to do so, expect to be held in contempt or similar coercion technique.
Bottom line: it doesn't work. Too bad.
gpg: Signature made Mon Jul 13 08:44:56 2009 PDT using DSA key ID 7D6F806C gpg: Good signature from "rsync.net <info@rsync.net>"
It's pretty easy to create a key that has that key id (since it's only the last few hex digits of the full 40 digit fingerprint) and the user id is freeform.
If you don't believe it's easy to pick your own key id, check the keyservers for the number of keys with DEADBEEF as their key id ;)
This has been around around a year: http://www.reddit.com/r/programming/comments/2ygi6/warrant_c...
Edit: HTML. Another edit: reddit.
This is better: http://rsync.net/products/encrypted.html
I don't know, that probably could have been written a week ago. Should we be worried?
:-P
No, it couldn't have, unless you have a time machine and a friend on the NYT's national desk, because it was in the Times today, not last week: http://lmgtfy.com/?q=In+opening+remarks%2C+a+Democratic+sena....
I agree with you that they could have found a story that would have been harder to guess.
http://video.economist.com/index.jsp?fr_chl=157a3251a697e23e...
Putting an actual quote in there makes it very secure.