desktop VS clients

There have been requests. So far there hasn’t been an easy way to implement it, unfortunately: https://github.com/bitwarden/desktop/issues/90

If you activate the 'minimize when copying to clipboard' option in preferences, but need to copy something that is set to require master password confirmation, Bitwarden just minimises without copying the password. I made a ticket for that in GitHub in august '21, but that was closed after a 'reorganization' in April. My head was not in the space to check for this problem then, but I checked it now and the problem persists with version 2022.8.1. Of cause I appreciate help with the actual problem, but how do I best let Bitwarden know that this problem persists?

I ended up installing previous version https://github.com/bitwarden/desktop/releases/tag/v1.33.0

$ rpm -qp —scripts https://github.com/bitwarden/desktop/releases/download/v1.33.0/Bitwarden-1.33.0-x86_64.rpm postinstall scriptlet (using /bin/sh): #!/bin/bash # Link to the binary ln -sf ‘/opt/Bitwarden/bitwarden’ ‘/usr/bin/bitwarden’ # SUID chrome-sandbox for Electron 5+ chmod 4755 ‘/opt/Bitwarden/chrome-sandbox’ || true update-mime-database /usr/share/mime || true update-desktop-database /usr/share/applications || true postuninstall scriptlet (using /bin/sh): #!/bin/bash # Delete the link to the binary rm -f '/usr/bin/bitwarden'

In 2019, an issue was opened in GitHub suggesting for the dev team to manage the flatpak application. Currently, the flatpak that is present in Flathub isn't official and this is a security risk, because that's about passwords.

Thanks for the feedback everyone, you can follow the latest updates for this issue on Github.

Thanks, these were the answers I was looking for too. Being a newb, which of these file links do I need to re-install on an old MacOS 10.11? https://github.com/bitwarden/desktop/releases/tag/v1.31.3

During all this, libsecret was updated which broke Webex (https://aur.archlinux.org/packages/webex-bin#comment-855518). Couldn't find a good way to downgrade a package so I ended up installing some fork of libsecret which got Webex working again. Also, there was an electron update which I think has caused Bitwarden to spew Javascript errors. Someone made a Github issue about the error and although I don't think he quite understands what he's doing, that looks like the same error I was getting - https://github.com/bitwarden/desktop/issues/1338.

Following an upgrade to version 1.31.0 of the Bitwarden desktop client, I noticed that I could no longer view OTP keys. I then discovered that my Premium status is no longer reflected in the desktop client, but I am indeed classified as a Premium member on the Bitwarden website. This appears to be a bug in version 1.31.0 and has been reported to the Github bug tracker: https://github.com/bitwarden/desktop/issues/1309

I didn't go chasing through all the typescript but I'd presume adding a new PassphraseGenerationStrategy https://github.com/bitwarden/clients/blob/desktop-v2024.3.0/...

Breaking: Open Source software have BUGS!

https://github.com/bitwarden/clients/issues/6560#issuecommen...

Bug fix for this has been merged last week. It is not in 2023.10 though, so you will have to wait for the next release of the web vault.

It's definitely out (https://github.com/bitwarden/clients/releases/tag/browser-v2... just looks like browsers haven't approved it yet.

I'm not sure about any specifics beyond that both are getting support for them (for the keepass ecosystem I'm sure about other mobile clients, but I don't think the feature request to support passkeys has been acknowledged by the keepass2android dev sadly). Here's the keepassxc PR with some details about the implementation, and what should be done in future work on passkey support: https://github.com/keepassxreboot/keepassxc/pull/8825

Bitwarden has a few blogs if you search for bitwarden passkeys, but from skimming one it didn't seem to go into technical details (though I didn't watch the videos). I guess you could look through the PRs: https://github.com/bitwarden/clients/pulls?q=is%3Apr+passkey... but I don't really feel like doing that.

Bitwarden has regular external audits (here is the 2022 audit) and the code (both server side and client side) is open source (here f.e).

/bitwarden_license directory

Now the secret manager is in the `bitwarden_license` directory so it is not a GPL covered product and not open source but covered by BITWARDEN LICENSE AGREEMENT [3]. It does not allow you to use it as OSS.

[1] https://github.com/bitwarden/clients/tree/master/bitwarden_l...