bitwarden-to-keepass icon indicating copy to clipboard operation
bitwarden-to-keepass copied to clipboard

Published 20 hours ago • verified publisher icon davidnemec

Make custom fields hidden by default

Open basbebe opened this issue 3 years ago • 2 comments

I know very little about the keepass format but I think it makes sense to make all custom fields added in Bitwarden "hidden" (or is it "secret"?) by default in the exported database.

Potential content of these fields is TOTP seeds, answers to security questions, PINs, recovery codes.

basbebe avatar Jan 13 '21 07:01 basbebe

Yes, I agree. But it's currently not supported by pykeepass but it has an open PR for this libkeepass/pykeepass/pull/186. So when/if this gets merged I will use it for sure.

But having them exported as "non-protected" does not make them less secure. They are "just" visible as plaintext when you unlock your database and view tab with custom properties.

davidnemec avatar Jan 13 '21 13:01 davidnemec

Great!

But having them exported as "non-protected" does not make them less secure. They are "just" visible as plaintext when you unlock your database and view tab with custom properties.

Yes I know – It would just more comfortable to have them hidden by default. (as opposed to hiding them "by hand")

basbebe avatar Jan 13 '21 13:01 basbebe

The pull request is already merged. Can we make the change? @davidnemec

ccfiel avatar Jul 15 '23 13:07 ccfiel