Live data from Hacker News

Bitwarden Acquires Passwordless.dev

bitwarden.com

71–80 of 399 posts

Re: Bitwarden Acquires Passwordless.dev

#72
post #68

I really dislike the idea of giving complete access to my digital life to any company, particularly one that needs to grow quickly. The tech for password vaults is so simple, I use keepass + icloud syncing and get free end-to-end encrypted password syncing, without sharing any data with anyone. Outlined in more detail here: https://magoop.substack.com/p/how-to-manage-500-passwords-se...

Agreed. I use keepass + dropbox secured with yubikey. You can even go a step further and configure yubikey with keepass as well.

Re: Bitwarden Acquires Passwordless.dev

#73
post #30
post #26

Earlier quoted context omitted.

I just switched password managers from LastPass, and Bitwarden's lack of multiple accounts on their browser plugin was a dealbreaker for me. Such a basic feature, especially if they want to get widespread adoption. Otherwise, anyone whose work uses Bitwarden basically can't also use it for their personal stuff without jumping through hoops.

Aren’t you supposed to have your personal Bitwarden account and get work passwords shared to your account? I thought that’s how Bitwarden for organisations worked.

Ideally I'd want to keep my _personal_ personal stuff separate from my "work personal" (ie my personal logins, but the one for work accounts) separate from my shared work stuff. So I'd want two accounts, one for my truly personal accounts, and then one for my work-personal and have the work-shared connected to that.

Re: Bitwarden Acquires Passwordless.dev

#74

One can easily self host a bitwarden server on digitalocean. https://bitwarden.com/blog/digitalocean-marketplace/ However, I'm curious what y'all think about the cost. A digitalocean droplet for the recommended specs (4 GiB memory) is $24/month. This is hard to stomach when you compare with Bitwarden Premium which is <$1/month. I guess it depends on how much you value your own data.

[flagged]

Re: Bitwarden Acquires Passwordless.dev

#75

One can easily self host a bitwarden server on digitalocean. https://bitwarden.com/blog/digitalocean-marketplace/ However, I'm curious what y'all think about the cost. A digitalocean droplet for the recommended specs (4 GiB memory) is $24/month. This is hard to stomach when you compare with Bitwarden Premium which is <$1/month. I guess it depends on how much you value your own data.

I run Vaultwarden on the free VPS from Google Cloud and it works great.

Re: Bitwarden Acquires Passwordless.dev

#76
post #73
post #30

Earlier quoted context omitted.

Aren’t you supposed to have your personal Bitwarden account and get work passwords shared to your account? I thought that’s how Bitwarden for organisations worked.

Ideally I'd want to keep my _personal_ personal stuff separate from my "work personal" (ie my personal logins, but the one for work accounts) separate from my shared work stuff. So I'd want two accounts, one for my truly personal accounts, and then one for my work-personal and have the work-shared connected to that.

There doesn't seem to be a security benefit of doing this if you encounter having to swap between personal-personal and work-personal.

It doesn't take me many seconds to swap accounts. LastPass allows you to be signed into two accounts at the same time in the same browser?

Re: Bitwarden Acquires Passwordless.dev

#77

Earlier quoted context omitted.

it's just WebAuthn with an easier to understand name. However passkeys depends on a yet to be published standard for QR codes + bluetooth + websockets for doing WebAuthn from a second device. But that is planned to be published soon.

Just recently tried to add WebAuthn to an app and was shocked at how complicated the spec is and how quirky the implementation ends up being. The biggest thing I couldn't easily figure out is how to use it properly. It seems like hybrid auth with your phone or FIDO gives you sign in, and local could be used for sessions? It's hard to make heads or tails from it. The developer UX was also pretty bad, ArrayBuffers was…

Webauthn L4 standardises on JSON serialisation luckily.

Yes the spec is horribly complex unfortunately.

In my own project I send the assertion and attestation as multipart/form-data. Which means I can just directly send the ArrayBuffers over the wire.

    PublicKeyCredential.prototype.toFormData = function (this: PublicKeyCredential) {
        const formData = new FormData()
        formData.append('type', this.type)
        formData.append('id', this.id)
        formData.append('rawId', new Blob([this.rawId]))
        switch (this.type) {
            case 'webauthn.get':
                if (!(this.response instanceof AuthenticatorAssertionResponse)) {
                    throw new Error('Unknown type')
                }
                formData.append('response.authenticatorData', new Blob([this.response.authenticatorData]))
                formData.append('response.signature', new Blob([this.response.signature]))
                formData.append('response.clientDataJSON', new Blob([this.response.clientDataJSON]))
                if (this.response.userHandle) {
                    formData.append('response.userHandle', new Blob([this.response.userHandle]))
                }

            case 'webauthn.create':
                if (!(this.response instanceof AuthenticatorAttestationResponse)) {
                    throw new Error('Unknown type')
                }
                formData.append('response.attestationObject', new Blob([this.response.attestationObject]))
                formData.append('response.clientDataJSON', new Blob([this.response.clientDataJSON]))
                break
            default:
                throw new Error('Unknown type')
        }
        return formData
    }

    async solveChallenge(challenge: Challenge, credential: PublicKeyCredential) {
        const formData = credential.toFormData()
        await fetch(challenge.location, { method: 'POST', headers: {'content-type':'multipart/form-data'}, body: formData })
    }

Re: Bitwarden Acquires Passwordless.dev

#78

I still don't understand how it works. I went into the website under authenticated using my phones API, where is my account now? There is nothing in my Bitwarden vault.

Passkeys are stored on your platform keychain. In time, Bitwarden will offer this interface up, so you can sync them through your Bitwarden vault.

Currently, if you use an iPhone, you will have the passkey stored in iCloud keychain. Your "account" is a private key held within iCloud keychain, along with some metadata mapping that private key to the site you visited.

Re: Bitwarden Acquires Passwordless.dev

#79
post #53

Earlier quoted context omitted.

Also Bitwarden recently raised 100M from VC so yeah, the clock is ticking now.

Ah for fuck's sake. It keeps happening to all the software I love. I guess I'll have to stop relying on convenience (I was a 1Password user years ago) and go 100% open-source. None of the libre offerings seem to be as convenient and polished, but at least they're not into some VC's pocket ready to squeeze as much profit as possible out of my paid membership. What's a good OSS alternative that works with iOS and Linux…

KeepassXC has served me well for many years, synced via my Nextcloud but could just as easily use dropbox or icloud, or even syncthing.

Re: Bitwarden Acquires Passwordless.dev

#80
post #67

Earlier quoted context omitted.

Vaultwarden's great. I use it. I use the Bitwarden Android client, though. Not sure what there is to replace that.

It's open source and can be forked if necessary: https://github.com/bitwarden/mobile

To add onto this, if you care about supply chain attacks, bitwarden mobile supports Fdroid builds (albeit not part of the main repo because they rely on xamarin) so you can host your own fdroid repo and run your own builds if so desired.
Post reply on HN