Facillitate DTC client backups #2
Description
At this time, dtc requires a Sqlite 3 database to store public metainformation about the keys it creates. Unfortunately, this brokes the signer if we lose the database.
Possible solutions:
- Create command in dtcconfig to recreate db given nodes information. The database might not be exactly the same (e.g. different Cryptoki IDs), but it should work seamlessly with previous applications.
- Remove dependency in the Sqlite3 database and save the configurations in dtc.yml file. This allows us to make backups of the client configuration with only one file, but it could not scale properly (Each key pair saves ~50 Sqlite3 rows with information).