4 ms·

You can just use bitwarden everywhere if you are ok with it in the cloud.

by EnPissant 8mo ago

rstat1 8mo ago
Doesn't need to be in the cloud for it work everywhere.
- deleted 8mo ago
  [deleted]
- EnPissant 8mo ago
  True. You can self-host.
arjie 8mo ago
I do use Bitwarden everywhere but a couple of times the passkey prompt doesn't show it. I think that's how I got the webview for one of my google accounts stored in iOS keychain.
- ezfe 8mo ago
  Anytime you save to your iOS keychain you’re doing so through the system prompt and Bitwarden should be included as a target option in that prompt. If it’s not, that’s a Bitwarden issue. 1Password shows up in the system UI regardless of context on iOS.
mkehrt 8mo ago
Tell that to my mom who has created a bunch of passkeys all over the place without knowing what they are. I'm trying to unwind it but it's a mess.
- goku12 8mo ago
  Passkeys are an antipattern in UX design. You want to make it simple for the users? Great! But stop treating them as too stupid to decide anything on their own. Stop locking them out of the decision loop and doing things behind their back. This is practically the corporate design philosophy of the past two decades. You can see this a lot in smartphone design. I keep asking what advantages passkeys offer over TLS self-signed client certificates. I haven't got any answers so far. Perhaps increase the security by encrypting the private key with a password or an external token. This is safe, like SSH and unlike regular passwords, because no secrets are sent to the server. TLS certs and (encrypted) keys are more tangible and easier to manage. Perhaps passkeys do offer some advantages over TLS certs. But can't those be added to TLS, rather than rollout an entirely new system? The infuriating part is that this facility exists in browsers. They just let it rot to an extend that it's practically unusable. Meanwhile, Gemini browsers are using it quite successfully (for those who use Gemini).
  - cyberax 8mo ago
    Passkeys ARE self-signed certs. You can store their private key on a hardware token, but you don't have to. Their only difference is the automated provisioning.
    - goku12 8mo ago
      > Passkeys ARE self-signed certs. So they took something that works well and created a bad UX around it, while ignoring the working, yet languishing UI/UX that was already around?
      - cyberax 8mo ago
        Self-signed certificates are in the 'barely working' state. They operate on a wrong protocol level, and they can't be provisioned by the website itself. If you try to describe how you _want_ the TLS client certificate UI to work, you'll end up with passkeys.
        goku12 8mo ago
        Okay. So they took a solution that was in a barely-working state due to their deliberate neglect, and still managed to give a bad new UX when they got the opportunity to rework it?
        0x0 8mo ago
        > "they can't be provisioned by the website itself." It's funny, we used to have a html tag that would exactly that: <keygen />
      - lxgr 8mo ago
        You can't be seriously claiming that self-signed PEM certificates were working well. I've been using them for years in various contexts, and they're an absolute nightmare. Despite all their faults, for the average user, Passkeys are still leagues ahead of GnuPG card, PIV, PKCS#15 etc.
      - lxgr 8mo ago
- ezfe 8mo ago
  “All of the place” meaning where? There’s only a few places you can put them and they’re all more secure than passwords so it sounds like not a huge issue.

You can just use bitwarden everywhere if you are ok with it in the cloud.

rstat1 8mo ago

Doesn't need to be in the cloud for it work everywhere.

deleted 8mo ago
[deleted]
EnPissant 8mo ago
True. You can self-host.

arjie 8mo ago

I do use Bitwarden everywhere but a couple of times the passkey prompt doesn't show it. I think that's how I got the webview for one of my google accounts stored in iOS keychain.

ezfe 8mo ago
Anytime you save to your iOS keychain you’re doing so through the system prompt and Bitwarden should be included as a target option in that prompt. If it’s not, that’s a Bitwarden issue. 1Password shows up in the system UI regardless of context on iOS.

mkehrt 8mo ago

Tell that to my mom who has created a bunch of passkeys all over the place without knowing what they are. I'm trying to unwind it but it's a mess.

goku12 8mo ago
Passkeys are an antipattern in UX design. You want to make it simple for the users? Great! But stop treating them as too stupid to decide anything on their own. Stop locking them out of the decision loop and doing things behind their back. This is practically the corporate design philosophy of the past two decades. You can see this a lot in smartphone design. I keep asking what advantages passkeys offer over TLS self-signed client certificates. I haven't got any answers so far. Perhaps increase the security by encrypting the private key with a password or an external token. This is safe, like SSH and unlike regular passwords, because no secrets are sent to the server. TLS certs and (encrypted) keys are more tangible and easier to manage. Perhaps passkeys do offer some advantages over TLS certs. But can't those be added to TLS, rather than rollout an entirely new system? The infuriating part is that this facility exists in browsers. They just let it rot to an extend that it's practically unusable. Meanwhile, Gemini browsers are using it quite successfully (for those who use Gemini).
- cyberax 8mo ago
  Passkeys ARE self-signed certs. You can store their private key on a hardware token, but you don't have to. Their only difference is the automated provisioning.
  - goku12 8mo ago
    > Passkeys ARE self-signed certs. So they took something that works well and created a bad UX around it, while ignoring the working, yet languishing UI/UX that was already around?
    - cyberax 8mo ago
      Self-signed certificates are in the 'barely working' state. They operate on a wrong protocol level, and they can't be provisioned by the website itself. If you try to describe how you _want_ the TLS client certificate UI to work, you'll end up with passkeys.
      - goku12 8mo ago
        Okay. So they took a solution that was in a barely-working state due to their deliberate neglect, and still managed to give a bad new UX when they got the opportunity to rework it?
      - 0x0 8mo ago
        > "they can't be provisioned by the website itself." It's funny, we used to have a html tag that would exactly that: <keygen />
    - lxgr 8mo ago
      You can't be seriously claiming that self-signed PEM certificates were working well. I've been using them for years in various contexts, and they're an absolute nightmare. Despite all their faults, for the average user, Passkeys are still leagues ahead of GnuPG card, PIV, PKCS#15 etc.
    - lxgr 8mo ago
ezfe 8mo ago
“All of the place” meaning where? There’s only a few places you can put them and they’re all more secure than passwords so it sounds like not a huge issue.