Designing Crypto Primitives Secure Against Rubber Hose Attacks (2012)
usenix.org
usenix.org
If I'm Mallet, I don't want people using passwords I can't quickly force out of them. Therefore, I pretend I don't know about this, or don't believe it, and keep using the rubber hose on people who are implementing this protocol. Therefore, those people get worked over longer and end up in a worse spot than people who are able to give up a password quickly. Net result is that people are terrified of using this stuff because they know that if they don't give up a working password quickly they'll be tortured longer.
Moral: This is probably a really good way to remember secure (that is, high-entropy) passwords. Don't pretend it's good for a use-case at which it is very obviously a horrible fit.
Of course, any actor that is willing to torture an answer out of you is probably willing to torture n answers out of you and/or watch you die in the process. This is one of those problems that there may not be a technological solution to and we should probably focus on spreading the concept of human rights to our children instead.
The eternal question of how to fight monsters without becoming one in the process.
People can be coerced into doing anything they would do normally (unlocking a lock; supplying their fingerprint; phoning their conspirator and saying to go ahead with the plan.) True coercion-resistance, I would think, implies that the mechanism has the ability to differentiate a stimulus supplied under coercion, even under the assumption that Mallet could have fed Alice some anti-anxiety drugs to regularize detectable symptoms of stress in her behaviour. (Coincidentally, "truth serums"—i.e. low-dose dissociative anaesthetics, ketamine or PCP being just as workable as sodium pentathol—also have anxiolytic effects. I can't imagine a state actor wouldn't take advantage of this if the goal is coercion rather than torture-for-the-sake-of-torture.)
As far as I know, there is one single useful mechanism for coercion-resistance: precommitment with counterparties. If Alice and Bob are supposed to have no further contact once the plan is in motion, and Bob knows this, then it is useless to torture Alice into contacting Bob—Bob will take the contact itself as a signal that Alice has been compromised.
You can automate this; if Alice (or her device) must attend regular KEx parties to get a new key (i.e. participate in a protocol with a security ratchet), then capturing her or her device prevents her from doing this, and so expires her key material (kicks her keys out of the keybag, basically.)
On the other hand, if you can remove the active mens rea component, this is a good solution. I imagine law enforcement is actively trying to prevent any software with a dead man's switch key-destruction component from ever becoming popular/ubiquitous, because it would enable people to claim they truly had no idea the software had a feature where their key would be destroyed in such a scenario; they were just using it because everyone else was. Imagine if BitLocker/FileVault had a mechanism like that, which could be forced on users by corporate policy!