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

Add support for encryption of binary data between SOH and ETX #13

Closed
Scottapotamas opened this issue Jan 12, 2018 · 1 comment
Closed

Comments

@Scottapotamas
Copy link
Collaborator

Allow the developer to provide a key or value which is used for some light crypto (optionally), to provide encrypted transport.

This would involve a minor refactor of message generation and ingest functions to support a compile time flag to enable encryption of messages.

@Scottapotamas Scottapotamas added this to Backlog in Base "Binary" Library via automation Jan 12, 2018
@Scottapotamas Scottapotamas removed this from Backlog in Base "Binary" Library Mar 12, 2018
@Scottapotamas
Copy link
Collaborator Author

This has been discussed a bit over the last week or so.

We don't really want to have this be a library feature, but there are items which can make it easier to swap out the protocol. See #77 etc.

The developer really should just provide the input/output scratchpad memory and do their own encoding as required.

Application Layer Functionality automation moved this from To do to Done Oct 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

1 participant