Export vault with integrity counters for comparison on import

Feature Requests Password Manager
, , , ,
1

For any platform with vault export/import capability:

(1) Add integrity counters on key data elements (e.g. Login, Card, Identity, Secure Note, etc.) and a checksum hash on the same elements’ associated data during export and import operations.
(2) Add counters for all categories of data excluded from the export operation by design (e.g. attachments).
(3) Provide a convenient means of saving or printing the counters on completion of the export or import. The saved information should include the date/time stamp of the export or import and the name of the file processed.

It is not enough to provide an export/import capability without a means of confirming its success or failure to re-establish the vault contents on import. Without such counters and hash the only reliable means for testing its success is a 100% verification by the user.

Once this feature is implemented, it will be a simple matter for the user to compare the comparable counters & hashes reported by the export to those produced by the import operation and conclude whether the import operation has successfully recreated the vault contents.

2

@ccaffee1 Welcome to the forum!

I think it’s a cool idea you have suggested.

If you want to address this issue while waiting for something like this to be developed, one work-around that may allow you to verify integrity if you’re importing into a new (empty) vault, would be to re-export the vault and then compare the hashes of the first and second export. Although now that I think about it, this approach probably won’t work so well until Bitwarden’s importer gets better at preserving time stamps and password histories.