We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
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.
Sorry, something went wrong.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: