3 ms·
Right. This goes back to the coercion issue, which I don't personally believe is valid. If one can be coerced to update a canary, then all bets are off. If they
by StavrosK 12y ago
Right. This goes back to the coercion issue, which I don't personally believe is valid. If one can be coerced to update a canary, then all bets are off. If they can't, there's no need to institute a grace period, as a canary won't ever be completely invalidated.
Obviously, the longer a canary stays outdated, the better the explanation should be, and I wouldn't trust a daily canary that started getting updated after six months, but I think missing one or two updates isn't that farfetched.
In Silent Circle's case, specifically, I don't think a NSL would have much utility, since we retain almost no customer data at all (only username/password, and optional email/name). I like the idea of automating the canary check message, though, and will write a script to do that right now, thanks.
- jacquesm 12y ago> Obviously, the longer a canary stays outdated, the better the explanation should be, and I wouldn't trust a daily canary that started getting updated after six months, but I think missing one or two updates isn't that farfetched. I don't see any factual difference between the two but I realize that humans are fallible. Note that you are still assuming that the only way a canary could be updated is by coercion, a keylogger installed at the right moment would allow one to update the canary absent the original updater just as well and as such I think canaries are of limited use. But if you do have one it should simply work as advertised. Isn't the real value for such monitoring in the future traffic and traffic analysis rather than the content or the customer data?