search

decentralized-identity / confidential-storage

Confidential Storage Specification and Implementation
https://identity.foundation/confidential-storage/
Apache License 2.0
78 stars 23 forks source link

Hub as Secure Messaging Server #81

Open OR13 opened 4 years ago

OR13 commented 4 years ago

Where do you put public keys that are ephemeral and rapidly changing, that are linked to long term keys commonly placed in the did document.

... they need to be plaintext... perhaps in a hub?

OR13 commented 4 years ago

@tplooker @csuwildcat do you want to elaborate on why secure messaging is a building block, why plaintext ephemeral keys are necessary for it, and how a hub might enable secure messaging / double ratchet / noise protocol?

OR13 commented 4 years ago

Related: https://github.com/decentralized-identity/didcomm-messaging/issues/66

OR13 commented 3 years ago

@csuwildcat to add comments here.

csuwildcat commented 3 years ago

Hubs should provide an interface by which certain objects that come through, that are typed in a specific way, are treated by standard Hub-standard logic as actionable messages (permission requests, drop-off messages, inquiries, etc.) that are circulated to the Hub owner's devices when they connect, in the same way push notifications are sync'd to devices today.

agropper commented 3 years ago

On Thu, Aug 27, 2020 at 4:57 PM Daniel Buchner notifications@github.com wrote:

Hubs should provide an interface by which certain objects that come through, that are typed in a specific way, are treated by standard Hub-standard logic as actionable messages (permission requests, drop-off messages, inquiries, etc.) that are circulated to the Hub owner's devices when they connect, in the same way push notifications are sync'd to devices today.

Fine, but I don't see what this has to do with storage. It seems that you're proposing standardizing some aspect of the Notification Service Endpoint Type.

Alternatively, you might be suggesting an Agent Service Endpoint Type where the first thing the Agent does when presented with a request is triage it into a standardized list of action categories. A "Request for resource access" would be one of the action categories that involve storage.