You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gocryptfs in their documentation mention: The old principle still applies: Important data should have a backup. Also, keep a copy of your master key (printed on mount) in a safe place. This allows you to access the data even if the gocryptfs.conf config file is damaged or you lose the password.
That's why I think it is important to warn user how important gocryptfs.conf is and tell them to back it up.
So that when bitrot happens on the config files or user accidentally delete it they can use the backed up conf.
Also I think having an unencrypted version of file as a backup is defeating the purpose of file encryption.
Describe the solution you'd like
Display a warning message after making a vault
The text was updated successfully, but these errors were encountered:
I don't think we should display this message after creating the vault, since this would probably getting annoying after some time. Maybe when starting Vaults for the first time, displaying this might be a good idea.
Regarding master key from the other issue, maybe we should expose it to the user, since it helps to protect against data loss.
gocryptfs in their documentation mention:
The old principle still applies: Important data should have a backup. Also, keep a copy of your master key (printed on mount) in a safe place. This allows you to access the data even if the gocryptfs.conf config file is damaged or you lose the password.
That's why I think it is important to warn user how important
gocryptfs.conf
is and tell them to back it up.So that when bitrot happens on the config files or user accidentally delete it they can use the backed up conf.
Also I think having an unencrypted version of file as a backup is defeating the purpose of file encryption.
Describe the solution you'd like
Display a warning message after making a vault
The text was updated successfully, but these errors were encountered: