3 ms·

> On confirmation, the grantor’s Master Key is encrypted using the grantee’s public key and stored once encrypted. Grantee is notified of confirmation. > When

by shakna 6y ago

> On confirmation, the grantor’s Master Key is encrypted using the grantee’s public key and stored once encrypted. Grantee is notified of confirmation. > When the request is approved or the wait time lapses, the public-key-encrypted Master Key is delivered to grantee for decryption with grantee’s private key. I'm not quite sure how I feel about the way they're doing this. Whilst this is a feature a lot of people desire, the way that they're doing it makes it feel like it would be impossible to verify that they're not storing your Master Key, or transmitting it to someone else - i.e. backdoor. At least, not with the level of detail I can find. [0] [0] https://bitwarden.com/help/article/emergency-access/ https://bitwarden.com/help/article/emergency-access/

judge2020 6y ago
I'm under the impression that the "encrypt master key with the receiver's public key" step is done on-client, so you could verify that the master key isn't being stored the same way you can very they're not sending the master key when logging into the web ui: looking at devtools and seeing everything that leaves the network.
- shakna 6y ago
  > I'm under the impression that the "encrypt master key with the receiver's public key" step is done on-client However, what would prevent them sending two public keys, one for your contact, and one for someone else? Or sending the wrong public key? How is the key exchange itself verified other than "Bitwarden user"? Those questions aren't answered.
  - warkdarrior 6y ago
    They are answered right in the help article: https://bitwarden.com/help/article/emergency-access/#confirm-an-accepted-invitation https://bitwarden.com/help/article/emergency-access/#confirm... "To ensure the integrity of your encryption keys, verify the displayed fingerprint phrase with the grantee before completing confirmation."
    - shakna 6y ago
      So keys aren't verified at all. That seems like something that needs more than a single sentence that comes _after_ they explain the confirmation process.
- e12e 6y ago
  It's a little too much to sort through on mobile, but I believe this is a reasonable place to start looking (this is the web app, the server might be worth a look too). As far as I can figure out, it's not part of the cli client. https://github.com/bitwarden/web/commit/3c5a972bc9e959c5ced989ff1a5702d0efea1ef7 https://github.com/bitwarden/web/commit/3c5a972bc9e959c5ced9... Reminder: bitwarden isn't just an awesome service, it's also committed to open source!

by shakna 6y ago

judge2020 6y ago

I'm under the impression that the "encrypt master key with the receiver's public key" step is done on-client, so you could verify that the master key isn't being stored the same way you can very they're not sending the master key when logging into the web ui: looking at devtools and seeing everything that leaves the network.

shakna 6y ago
> I'm under the impression that the "encrypt master key with the receiver's public key" step is done on-client However, what would prevent them sending two public keys, one for your contact, and one for someone else? Or sending the wrong public key? How is the key exchange itself verified other than "Bitwarden user"? Those questions aren't answered.
- warkdarrior 6y ago
  They are answered right in the help article: https://bitwarden.com/help/article/emergency-access/#confirm-an-accepted-invitation https://bitwarden.com/help/article/emergency-access/#confirm... "To ensure the integrity of your encryption keys, verify the displayed fingerprint phrase with the grantee before completing confirmation."
  - shakna 6y ago
    So keys aren't verified at all. That seems like something that needs more than a single sentence that comes _after_ they explain the confirmation process.
e12e 6y ago
It's a little too much to sort through on mobile, but I believe this is a reasonable place to start looking (this is the web app, the server might be worth a look too). As far as I can figure out, it's not part of the cli client. https://github.com/bitwarden/web/commit/3c5a972bc9e959c5ced989ff1a5702d0efea1ef7 https://github.com/bitwarden/web/commit/3c5a972bc9e959c5ced9... Reminder: bitwarden isn't just an awesome service, it's also committed to open source!