I see — thank you for clarifying!
1 Like
Can you have the source code audited by some official service, so I can be sure my passwords wont get stolen by this?
It will be safer than the clipboard.
Bitwarden, please don’t let silliness like this slow this any more than it already has been.
2 Likes
The code is publicly viewable (and downloadable/compilable) on the GitHub repo. Third-party code audits are not free, but you absolutely have the option to hire some security firm to audit @Quexten’s code. I hope that you will share the audit results publicly when you receive them.
4 Likes
Auditing costs money, and this is a project I do in my spare time for free, which already “costs” me a lot of hours, so I cannot hire any external contractor to audit it. I’m open to getting the project audited if you want to finance that 
If you think the maintainer (me) is malicious, I do have my real identity tied to it, as a maintainer, and reside within the EU, so I would be pretty stupid to try to steal credentials using this open source project, as in most EU countries you would definitely get jailed for that.
As for accidentally introduced security flaws, the threat model here would be either pulled in dependencies (some upstream library) being malicious, or some local attack against the app (other applications running on your local system), as it uses the same end to end encryption that all other Bitwarden clients use.
But if you are paranoid (which may be reasonable), and can’t / won’t audit the source code for yourself, and don’t have trust that others would do so, then you should probably stick to the official clients (which do not have this feature at the moment).
As @grb mentions, the source code is public, and the public builds are only ever built by the CI pipelines, the output log of which are also public. I don’t know whether they are bit-for-bit reproducible yet, specifically because of the C bindings of libfido2.
Anyways, it’s only a voluntary offer that I posted here in case it helps people. I’m not trying to convince anyone to use my tool.
3 Likes
Lol, im no programmer and will not request an audit.
I just wont use this software as I dont trust some random third party.
Would be great if the features from that App would be implemented into Bitwarden though.
Hopefully, you don’t have your Bitwarden account configured to use Argon2id as the KDF algorithm, then, since that code was written by the same “random third party”. 
4 Likes
That alone demonstrates how much you’re not a software developer, @Shadily4224. Bitwarden probably has 40 dependencies, each themselves dependent upon 10s to 100s of dependencies, almost all written by 3rd parties.
I never claimed to be a software developer?!
@Shadily4224, I referred to
Just replying to express interest in this being a feature. Our company could save several minutes per user, per day if this feature were implemented. We have hundreds of users on Bitwarden and this feature would be greatly appreciated!
1 Like
The best way to do that is to click “vote” at the very top of this window (scroll way up).
1 Like
Did that already, but considering 900+ people have already done that and we don’t have the feature after 6 years… ya know.
5 Likes
That is an astoundingly useless response to a user request. - Especially to one that is by now common among desktop secret managers, to clarify: Bitwarden is lagging behind the field in this issue.
The fact that “some users don’t want this” was never a valid argument when talking about a feature that users can choose to use.
4 Likes
@richard.wonka Welcome to the forum!
However, you have read that 2-year old comment completely out of context. That was a direct response to the immediately preceding comment, in which a user asked why anybody would want to use the Desktop app, given the lack of auto-fill functionality. Of course the explanation is going to mention that some users still use the non-autofilling Desktop app because even though they have no need for auto-fill, they wish to use the other unique capabilities of the Desktop app!
There was never an implication that Bitwarden was not considering this feature request because “some users … prefer not to use the auto-fill function”, which is how you seem to have interpreted the comment.
Besides, the user to whom you responded has since left Bitwarden. The most recent statement from Bitwarden in this thread is the following one:
2 Likes
Hello grb,
I did indeed interpret the response as you have described. As such I an relieved to hear that this was a misinterpretation.
Given the age of the feature request, the very nature of the feature and development in other secret management software, I’m still somewhat surprised at the slow trickle of news on the topic and still not finding this feature in the app.
I had read the last statement from half a year ago, by the way, and am welcoming the slight glimmer of hope, as I am coming to appreciate the rest of the software more and more.
Looking forward to more news on this!
3 Likes
I hope this key feature will be implemented before i die 
5 Likes
A much needed feature!
+1 for me on this.
I still keep keepassx on the side for those times when I need to fill in logins of desktop apps.
1 Like
This is now going so many years. Honestly I’m pretty disappointed on the communication as well as the requirements of users. The feature roadmap is way to high level and there is not really a chance on getting a feeling on how honest the bitwarden team is in communication. Always is the topic somehow in “work” - thats how you loose trust. As a new user this could be the topic why you are not starting with bitwarden.
8 Likes
+1
make it like the KeePass feature!
1 Like