Changes between Version 3 and Version 4 of PlainTextPasswords

Timestamp:

May 9, 2007, 2:48:35 AM (17 years ago)

Author:

lschiere

Comment:

--

PlainTextPasswords

@@ -24 +24 @@
  * '''Store the password in plain text and control access to the file.''' This is what Purple does: the password is in {{{accounts.xml}}} in plain text, but the file itself is only readable by its owner.  We allow the user to determine under what conditions sensitive files should be opened (if at all), and what constitutes a breach of security.
  * '''Lastly, you can not store passwords at all.''' This is Purple's default, and by far the most secure of all of the options.
+
+If you really wanted to, you could write a script to wrap Purple that 
+would decrypt {{{accounts.xml}}} and re-encrypt it when Purple exits.
+You wouldn't be able to encrypt it while Purple is running,  because Purple 
+writes to {{{accounts.xml}}} for things like info change.  This would 
+minimize your exposure time unless (like me) you run Purple nearly 24/7. 
+Personally, I feel that on any decent operating system, if someone can get to 
+your files you should either be able to trust the person to not touch 
+them, or you shouldn't be storing sensitive information there at all.