Repository navigation
Keys.dat should only contain private keys #256
Description
The existing keys.dat also contain application settings/preferences.
I suggest the following:
- keys.dat - only contains primary keys
- settings.dat - contains all settings/preferences for the application
This will allow users to backup the most important data, their private keys, independent of the application settings.
Metadata
Metadata
Assignees
Labels
No labels
Activity
Atheros1 commentedon Jun 25, 2013
I see no reason to separate them. This would just give people an additional file to worry about backing up.
fiatflux commentedon Jun 25, 2013
I strongly agree with the separation, as the two types of data serve very
different purposes and have very different sensitivity requirements. If I
wanted to share my settings with someone, as I did recently, I need to take
special care to not accidentally send my private keys.
r14c commentedon Jun 25, 2013
I don't think that is the most important concern when it comes to privacy software. The most important concern is security. Key files should only be user readable (an AppArmor profile on Ubuntu could be used to limit application access), it really doesn't matter who reads your config because it can't be used to decrypt your messages or impersonate you.
Dokument commentedon Jul 1, 2013
Honestly the config settings, key data, sent message data (such as plain text messages), addressbook, and subscriptions (, and chans in the future) could be used against a user if access is gained. I would agree more with making messages.dat ONLY encrypted messages and putting the other data in (a) different file(s).