Option to remove private user data hash, or two-way encrypt

[GoogleCodeExporter]

Currently certain private data is automatically one-way hashed.  This is the 
desired behavior in most cases, but some experiments require access to the raw 
data.  There should be an option to not has these fields, or to two-way encrypt 
them with a separate key than the file encryption key.

Original issue reported on code.google.com by alan.gar...@gmail.com on 20 Nov 2011 at 8:04

[GoogleCodeExporter]

Configuration options:
(one way, 2 way, plain text) (salt, encryption key)

Should have a global option, as well as the ability to override per probe.

Applications, such as the Journal app, should notify users that their 
information is visible to the organization collecting it.

Original comment by alan.gar...@gmail.com on 23 Nov 2011 at 10:09

[GoogleCodeExporter]

This would be useful in cases where the text and timestamp of the SMS message 
adds context to the data that Funf is collecting. I am using funf journal to 
collect training data for machine learning, and have considered using SMS to 
add some context to the sensor data, so this would be useful for that.

Original comment by iver.b...@gmail.com on 30 Jan 2012 at 1:25