Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

Discuss procedure of Masked Authenticated Streaming Data #518

Open
howjmay opened this issue Mar 16, 2020 · 2 comments
Open

Discuss procedure of Masked Authenticated Streaming Data #518

howjmay opened this issue Mar 16, 2020 · 2 comments
Assignees
Labels
A-mam Area - MAM C-feature Category - feature C-investigation Category - Investigation P-high Priority - High, important issues or features

Comments

@howjmay
Copy link
Contributor

howjmay commented Mar 16, 2020

We are going to implement a general abstract layer for MAM. This abstract layer includes a secure procedure to communicate between tangle-accelerator and TA-endpoint.

The request/response format have been presented in #513

See more information in note

@howjmay howjmay added P-high Priority - High, important issues or features C-feature Category - feature C-investigation Category - Investigation A-mam Area - MAM labels Mar 16, 2020
@howjmay howjmay added this to the MilleCrepeCake milestone Mar 16, 2020
@howjmay howjmay pinned this issue May 25, 2020
@howjmay
Copy link
Contributor Author

howjmay commented May 25, 2020

We should evaluate the performance of the current implementation. We apply quite a lot of encryption process which may cause sending a MAM message much longer than we expected or even more than implement MAM on endpoint.

@howjmay
Copy link
Contributor Author

howjmay commented May 25, 2020

To protect application which is using Noise Framework from man-in-the-middle attack, the client and tangle-accelerator must share the same Prologues. We need to figure out how to share this prologue among all the clients and tangle-accelerator

@howjmay howjmay unpinned this issue Jul 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-mam Area - MAM C-feature Category - feature C-investigation Category - Investigation P-high Priority - High, important issues or features
Projects
None yet
Development

No branches or pull requests

4 participants