<div dir="ltr">In
the prototypes we built, we've considered encryption as a way to
protect transient data so it can be transferred safely between people.<br><span class=""></span><div>e.g. we're not thinking about apps like encrypted shared resources that would stay in that state "for ever".<br><br></div><div>So I made the assumption that if a password gets reset, people would have to resent the data. <br><br></div><div>I agree it sucks tough, in terms of UX, since we would need to update the directory when this happens, and maybe have all the apps<br></div><div>do something special.<br></div><div><br></div><div>That's what is currently happening when you loose your pgp key and people are still sending you e-mails using it,<br></div><div>and that's why open pgp users directory evolved into sks services so deprecated keys would be less present on the web.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 19, 2014 at 12:48 AM, Ryan Kelly <span dir="ltr"><<a href="mailto:rfkelly@mozilla.com" target="_blank">rfkelly@mozilla.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 19/12/2014 10:42, Christopher Karlof wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Thu, Dec 18, 2014 at 3:45 AM, Tarek Ziade <<a href="mailto:tarek@mozilla.com" target="_blank">tarek@mozilla.com</a><br></span><span class="">
<mailto:<a href="mailto:tarek@mozilla.com" target="_blank">tarek@mozilla.com</a>>> wrote:<br>
<br>
Following up yesterday discussions on encryption key, I've started<br>
to prototype a "Key Directory" service.<br>
<br>
The goal of the service is to allow people to discover other<br>
people's public keys in the context of a 3rd party application, in<br>
order to be able to do end-to-end encryptions of app data.<br>
<br>
The two use cases we have in mind are:<br>
<br>
- The password manager<br>
- A file sharing application<br>
<br>
If users are collaborating on something encrypted, then key(s) used to<br>
encrypt that thing need to be stable. If users lose a shared resource<br>
because someone reset their password, that is bad.<br>
<br>
This makes me wary about using kB for any part of this infrastructure,<br>
although we might find a way.<br>
</span></blockquote>
<br>
Conversely, some users may see using kA as little better than using no encryption at all.<br>
<br>
Perhaps we will eventually need to revisit the user-choice option here, allowing each user to choose between recoverability and security/paranoia. But that's a very wriggly can of worms.<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
Ryan<br>
</font></span></blockquote></div></div>