Reader Comments

Subscribe: RSS

View by: Time | Thread

• 

  Ed Halley, 15 Aug 2003 @ 10:56am

  
  

  No Subject Given

  In such cases, the applications save very simplified "dumps" of their internal data structures including the recent revision history and other elements. They do this for two reasons: it's faster, and having editing records enable neat "group" work flow concepts.
  
  Two ideas come to mind:
  
  (1) disable the fast-and-historical save options until the user specifically chooses to enable them; the oblivious user should be protected.
  
  (2) when you save historical information, save it encrypted by default. The worst case is when the user can't unlock their own hidden historical data, which isn't all that bad. Encrypt to a machine+user specific metric, which automatically unlocks when opened by the same detected machine+user, or offer a more complete encryption path that encrypts according to a provided pki or simple password. Even WEAK encryption would be a big win here, but there are plenty of much stronger crypto standards *built into everyday operating systems*.

  [ link to this | view in chronology ]

• 

  Anonymous Coward, 16 Aug 2003 @ 11:48pm

  
  

  here are the Microsoft articles on this

  Here are the Microsoft articles on this
  http://support.microsoft.com/default.aspx?scid=kb;EN-US;211209
  http://support.microsoft.com/defau lt.aspx?scid=kb;EN-US;197978

  [ link to this | view in chronology ]