You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2023. It is now read-only.
In order to support arbitration, we enable users to send their shared keys to arbitrators for message auditing. We need to handle expiration of those keys so that arbitrators cannot continue to eavesdrop on conversations that may arise involving the same participants. We need to also define the circumstances under which the key should expire. Should it happen automatically after the dispute is resolved? Should the participants explicitly revoke the arbitrator's access? Should a new shared key be generated each time one is sent to an arbitrator, effectively limiting the scope of the arbitrator's access to only messages that were sent prior to the grantor's explicit action?
In order to support arbitration, we enable users to send their shared keys to arbitrators for message auditing. We need to handle expiration of those keys so that arbitrators cannot continue to eavesdrop on conversations that may arise involving the same participants. We need to also define the circumstances under which the key should expire. Should it happen automatically after the dispute is resolved? Should the participants explicitly revoke the arbitrator's access? Should a new shared key be generated each time one is sent to an arbitrator, effectively limiting the scope of the arbitrator's access to only messages that were sent prior to the grantor's explicit action?
😅 This is not a v1 priority. cc @wanderingstan
The text was updated successfully, but these errors were encountered: