{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreici27l6vhb3wkdlcrvrmqp3aw2fpofbesrzgkqpjobtrqujalzmd4",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3ml24qrcw2332"
  },
  "path": "/t/confer-end-to-end-encryption-for-ai-chats/34439?page=2#post_28",
  "publishedAt": "2026-05-04T14:53:28.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "Bitwarden Community Forums – 3 Mar 25",
    "Support for Storing PRF-Capable Passkeys in Bitwarden Vault"
  ],
  "textContent": "Just wanted to share an update for those still trying to get in: you can now sign up/log in to confer.to using a recovery code instead of being forced into passkey setup right away.\n\nThe issue isn’t passkeys in general; it’s the specific type of passkey that Confer uses. Confer leverages WebAuthn with PRF (Pseudo-Random Function) extension, which allows the passkey to derive encryption keys. This is essential for their E2EE architecture, but it’s still a relatively new feature and Bitwarden doesn’t support it yet:\n\nBitwarden Community Forums – 3 Mar 25\n\n### Support for Storing PRF-Capable Passkeys in Bitwarden Vault\n\nFeature Requests Password Manager\n\nserver:default-cloud app:all security\n\nTalking about the implementation of Passkeys where the Bitwarden Extension/App acts as the A in CTAP. (Authenticator) PRF support → For one of my accounts, I have Bitwarden master password in Bitwarden. I was planning on adding my Bitwarden as a...\n\nReading time: 9 mins 🕑 Likes: 181 ❤",
  "title": "Confer: end-to-end encryption for AI chats"
}