-
Notifications
You must be signed in to change notification settings - Fork 763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E2E Encryption: Support more keyring strategies #1585
Labels
Comments
om26er
changed the title
E2E Encryption: Support custom keyring strategies
E2E Encryption: Support more keyring strategies
Jul 28, 2022
pls see my comments #1586 (comment) - which roughly apply here as well. "E2Ev2" is the way forward, not "E2Ev1" ... but even more so, we need to have a proper design and spec first (eg wamp-proto/wamp-proto#417) before jumping into moving code around ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a platform which runs a WAMP router, that system also has a secure element. each user (mobile phone / website) has their own public/private key generated on login. The current implementation in autobahn ties the Key (mix of originator and responder keys) to a URI.
This is mostly fine however in our case it is desired to have 1 responder and multiple originators, the originators can dynamically change as people are added/removed from the system.
From the look of it, it is currently not possible with the autobahn-python API. There are two changes that I think will make the above possible
Key
object should support multipleoriginators
(a list)enc_key
in the Invocation should be used to determine if the originator is "expected"The text was updated successfully, but these errors were encountered: