-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add support for server-side ephemeral keys #298
Labels
Comments
I suggest we look at |
To add one more comment to this topic. The improvement will provide us with:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we use an ECIES algorithm with fixed keys (master server public key, device public key) that are stored on the mobile device and client-side ephemeral keys. This is good, but we could also add support for the server-side ephemeral keys (let's call them "temporary keys" here).
Gist
Temporary Public Key Exchange
=> Client now has a new one-time public key
Temporary Key Pair Storage on Server-Side
Server (probably PA Server) should store temporary keys in a separate table, such as
pa_temporary_keypair
. Each record should be one-time-only (when used, it should invalidate) and should have short expiration (to allow the cleanup).Encrypting Request and Response
The encryption/decryption works the same way as for our current ECIES. The temporary key should be invalidated once the encrypt/decrypt cycle is completed.
The text was updated successfully, but these errors were encountered: