Skip to content
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

Create a display timeout for encrypted memo field contents #3219

Open
blockops1 opened this issue Apr 26, 2018 · 2 comments
Open

Create a display timeout for encrypted memo field contents #3219

blockops1 opened this issue Apr 26, 2018 · 2 comments
Labels
D-forward-secrecy-vs-recoverability Design issue: Forward secrecy vs recoverability M-user-support User support issue question

Comments

@blockops1
Copy link

The issue is the encrypted memos last forever.

Would like to request a feature for the encrypted memo field on shielded transactions. If I send an encrypted memo to someone, it is probably because I want it kept private or anonymous. I don't want the compromise of my private key to enable someone to retrieve the entire history of conversations that I have.

Would it be possible to add a time or block number field to a shielded transaction after which the encrypted memo is not able to be recovered or displayed?

@str4d str4d added the question label Apr 26, 2018
@ioptio ioptio added the M-user-support User support issue label Apr 30, 2018
@ioptio ioptio added this to Blocked in User Support Apr 30, 2018
@leto
Copy link
Contributor

leto commented May 7, 2018

@blockops1 just to clarify, if your private keys are stolen, the attacker can only see memos you have received, not those that you have sent. The sender has no knowledge of the contents of the memos it has sent in the past, it's not stored anywhere locally. Only the receiver has it and if the reciever's private keys are stolen, that is when your sent messages would be seen.

This feature does not immediately seem possible, without some large changes, due to how JoinSplits work. The sender has no control over when the receiver can look at memo data, they have no control over that at all.

@blockops1
Copy link
Author

@leto I appreciate the clarification. It would seem to me if private keys could be used to encrypt and send a shielded transaction with a message and then in the future create a display key or a payment disclosure key that it may be possible to reveal the contents of the encrypted memo field.

And as regarding the time out of the message for the receiver, I understand it would require significant changes to the Joinsplits so I figured the earlier to request it be placed on the road map the more of a chance it could be enabled within a few years.

@mdr0id mdr0id added the D-forward-secrecy-vs-recoverability Design issue: Forward secrecy vs recoverability label Jun 7, 2018
@mms710 mms710 added this to Needs Prioritization in Arborist Team Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D-forward-secrecy-vs-recoverability Design issue: Forward secrecy vs recoverability M-user-support User support issue question
Projects
Arborist Team
  
Needs Prioritization
User Support
  
Blocked
Development

No branches or pull requests

5 participants