Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Encryption and risk



On Oct 6, 2009, at 10:27 AM, Dan Ritter wrote:
> Everyone seems to be ignoring the real brute force attack:
> rubber-hose cryptanalysis.

I did not ignore it; I simply chose not to address it.  But since you  
asked... :)

Obviously, no algorithm can be proof against a rubber hose attack.   
Securing against rubber hoses is a matter of implementation.  One  
possible mechanism is something similar to standard code signing  
practice with multi-factor authentication.  The user has a pass phrase  
(virtual key).  The site has a hard token of some sort.  That token is  
stored in a secured area (physical key).  The user does not have  
access to said secured area and must make a request through physical  
security to sign out the token and sign it back in after the code  
signing is complete.  And, of course, physical security monitors the  
checked-out token at all times.

--Rich P.







BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org