After removing a record database can no longer be decrypted

oxur / rucksack

A terminal-based secrets manager, generator, and importer/exporter (Firefox, Chrome) backed with a concurrent hashmap

Apache License 2.0

12 stars 1 forks source link

After removing a record database can no longer be decrypted #59

Closed oubiwann closed 1 year ago

oubiwann commented 1 year ago

Almost certainly this is a bug in the new rm subcommand.

oubiwann commented 1 year ago

Confirmed: commenting out the line util::remove_by_key(&app.db, key)?; in cli::command::rm allows the DB to be decrypted in successive operations.

Nothing fancy is happening, so not sure what could be causing the problem ...

oubiwann commented 1 year ago

One way around this might be:

don't delete
instead, add an "active" metadata field
change rm to set active=false
don't list records with active=false
don't export records with active=false (unless a --with-inactive flag has been passed ...)

oubiwann commented 1 year ago

Also, there could be a config option: "purge inactive upon quit"