App can now be used to create and sign in with passkeys.

Some further context:

Right now the mobile apps are using a Framework called Xamarin which enables crossplatform mobile releases. Since it has become a roadblock for them (e.g. needed to wait for Microsoft to support passkeys in Xamarin) they are planning to switch to native apps (Swift for ios and Kotlin for android). Source

cross-posted from: https://lemmy.world/post/14912799

Bitwarden Authenticator is a standalone app that is available for everyone, even non-Bitwarden customers.

In its current release, Bitwarden Authenticator generates time-based one-time passwords (TOTP) for users who want to add an extra layer of 2FA security to their logins.

There is a comprehensive roadmap planned with additional functionality.

Available for iOS and Android

Given that passkey support has been out for a few months, I'm wondering if you've switched any of your existing logins?

BitWarden is my password manager of choice, I use it a lot. But one thing I find frustrating and honestly, nonsensical, is why it doesn't support ports out of the box? I have a bunch of services on different ports and would hope BitWarden would recognise that, but it doesn't? It's not a huge thing as I can always search, but it's one of those little niggly things.

I have what may be a stupid question...

How is it your master password is both used to decrypt your vault and used to authenticate with bitwardens public servers to acquire a copy of your vault/view it in the web app, but bitwarden can't use that password entry to decrypt the vault themselves?

(please correct me if I'm misunderstanding, as I use self-hosted vaultwarden for my server instead of the public ones)

I'm wondering how many are self hosting and if there's any benefits to doing so?

I’m hearing people really love 1password. I believe they also were the first ones to come up with a mobile-friendly implementation prior to iOS/Android support for third party password managers.

Seems like 1password has been and is on the ball as far as having the freshest features the fastest.

Has anyone heard of a timeline for this to be implemented? All I've heard is "soon".

Autofill with the extension seems broken for me. Anyone else with the issue?

I heard they were going to release it in August, but nothing happened yet.

ProtonPass JSON is not accepted for import to Bitwarden. I have searched for information about it but I can't find the answer to this problem. Could someone provide a solution?

I remember 1 year ago, asking on how to get it running on 4.4.2, but no one told me how to get it to run. So here's how to get it on Android 4.4.x. There are 2 methods to get it to run:

1. With Kiwi Browser (recommended, gets security updates even tho its an older version)
2. With Firefox (not recommended as it's pretty old)

1) With Kiwi Browser (recommended as it still gets security updates)
1. Install the last supported Kiwi Browser for Android 4.4
2. Go to crx4chrome and download an older extension of Bitwarden (preferably the first 2022 one)
3. Go to extensions and enable dev mode, and load that crx extension!
4. Enjoy Bitwarden on Android 4.4.x!
_________________________________________________________________________________
2) With Firefox 68
1. Install Firefox 68
2. In Firefox lookup Bitwarden version history for Firefox, then find one of the first 2022 versions. I tried the first 2022 version and it worked, I didn't try the few newer 2022 ones, as the first one just worked but you can try newer if you want.
3. Install it.
4. Go to about:config, search for extensions.update.enabled and toggle it. This will disable auto updates of extensions, so bitwarden does not auto update, making the extension not work.
5. Enjoy Bitwarden on Android 4.4.x!

Edit (Update/Correction):

It looks like I was very likely wrong (a good thing in this case!).

According to this entry in the official Bitwarden Help Center bitwarden[.]net is official too!

Its still weired that the login failed multiple times and bitwarden[.]net doesn't redirect to the homepage, as the other official domains do, and so on.

Nonetheless, all seems to be fine, gladly. Thanks for your input.

I've tried to log into Bitwarden and used vault.bitwarden[.]net, it failed. Also, this page is the only one on this domain (nothing on bitwarden[.]net) and the SSL Certificate differs.

vault.bitwarden.com (and bitwarden.com) behaves as expected.

I think I've actually used a phishing site. 2FA probably safed me pretty hard. Changed creds.

Has anyone seen anything recently on an ETA for passkey support in Bitwarden? A recent blog post mentioned "summer"... but I'm in the southern hemisphere so am not entirely sure when this refers to.