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
Hi team!
I'm sorry to make noise here, but I couldn't figure out another way to reach you (mailing elastic directly seemed an overkill) 😅
I am preparing an article where I am leaning about data encryption basing on your library and to sum up my findings, I have created a flow.
My main request would be: could anyone took a look at it and confirm that it is correct and I did not misunderstood anything? I would hate to spread false knowledge (I'm living the direct link, the comments there are enabled).
My side extra request would be clearning below sentence if someone has enough time:
Receiver decrypts AES key using the private key that corresponds to the public key used for encryption
I do not grasp how the Receiver knows the value of the public key? Seems to me that the only two thing it gets from the Mediator is the encrypted AES key and the encrypted payload 🤔
The text was updated successfully, but these errors were encountered:
Hi team!
I'm sorry to make noise here, but I couldn't figure out another way to reach you (mailing elastic directly seemed an overkill) 😅
I am preparing an article where I am leaning about data encryption basing on your library and to sum up my findings, I have created a flow.
My main request would be: could anyone took a look at it and confirm that it is correct and I did not misunderstood anything? I would hate to spread false knowledge (I'm living the direct link, the comments there are enabled).
Link: https://whimsical.com/request-cryptography-library-flow-KSi5XkkYErzoTwxWLX2NYR
My side extra request would be clearning below sentence if someone has enough time:
I do not grasp how the Receiver knows the value of the public key? Seems to me that the only two thing it gets from the Mediator is the encrypted AES key and the encrypted payload 🤔
The text was updated successfully, but these errors were encountered: