Improvements to hidden fields

[overexertyearly (Bob)]

Currently, the vault (tested on Android) will show a number of asterisks/dots that matches the number of characters in hidden fields and the password field. This is a security risk. Please make all hidden fields and password fields in the vault standardized by having all of them show a fixed number of asterisks/dots to avoid guessing from third parties. Ideally, all notes would also be hidden by the default or at least there should be an option to toggle automatically “hiding of all notes”.

[DenBesten]

Please create two separate feature requests. I might be willing to vote for a fixed number of dots, but I absolutely do not want notes to be hidden by default.

[Nail1684]

@overexertyearly I now closed this request (with a delay) for the reason @DenBesten stated.

[Nail1684]

@overexertyearly @DenBesten There actually is an existing feature request (and a bug report) for the “fixed number of dots”-part:

Standardize Password Concealment Across All Platforms

Currently, Bitwarden handles password concealment inconsistently across platforms: On the Windows desktop app, concealed passwords always display as six dots (••••••), regardless of length. This prevents someone from deducing password length. On the Android app and browser extension, concealed passwords match the actual length (e.g., a 12-character password shows 12 dots), which could unintentionally reveal information about the password. For consistency and security, I propose that Bitwarden…

 
… and I just found an existing feature request for the second “hiding of all notes”-part:

Hide notes column by default

Option to always keep the notes hidden always or selectively…

[grb]

This thread could, perhaps, be re-opened as a request strictly about the length of hidden information in custom fields of the "hidden " type (not passwords fields), since the existing feature request and the associated GitHub issue are limited only to password fields.

But unless @overexertyearly is willing to modify their OP accordingly, it may be best to simply close this thread and allow a new feature request to be started.