feat: TSP message types and optionally encrypted StreamPoster #935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows the
StreamPoster
to wrap the message stream in ESSR. Default is not to use it. I thought about doing this in KERIA but I think it's quite useful here. Tested e2e with full IPEX grant/admit in KERIA/Signify and works.For now doesn't work with forwarded messages to mailboxes or witnesses but can be extended, at least once this has been reviewed. (I also want to avoid the list copy on line 360)
This will prepend the stream with the proposed TSP message type
SCS
from Sam: #612 (reply in thread)I created a
Tsper
class similar toIlker
for the 3 new TSP message types.