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
I share my Mooltipass device with a number of non-technical family members who do not make regular backups of their password database. I would like to do the backing-up of their password database for them but the Moolticute application requires a user's card to be present/unlocked and (as I understand) only backs-up the password database of the user whose card is currently present/unlocked.
Feature
Allow the entire password database (for all users) to be exported in one operation, even if no user card is present.
Since the export is encrypted with AES-256, I see no security weakness here.
Justification
One family member (the diligent, technical person) can perform the password database backups for all other family members.
Workarounds
I've found a not-so-secure workaround which is to have copies of all the user's cards, all with their PINs set to something that I know, store these copies in a safe place and get them out when I want to make backups. Make the password database exports one-by-one.
The text was updated successfully, but these errors were encountered:
bitcog
changed the title
Export All Databases of File Without Need For Cards
Export All Databases to File Without Need For Cards
Jan 20, 2024
Missing feature
Background
I share my Mooltipass device with a number of non-technical family members who do not make regular backups of their password database. I would like to do the backing-up of their password database for them but the Moolticute application requires a user's card to be present/unlocked and (as I understand) only backs-up the password database of the user whose card is currently present/unlocked.
Feature
Allow the entire password database (for all users) to be exported in one operation, even if no user card is present.
Since the export is encrypted with AES-256, I see no security weakness here.
Justification
One family member (the diligent, technical person) can perform the password database backups for all other family members.
Workarounds
I've found a not-so-secure workaround which is to have copies of all the user's cards, all with their PINs set to something that I know, store these copies in a safe place and get them out when I want to make backups. Make the password database exports one-by-one.
The text was updated successfully, but these errors were encountered: