Put in RPK and callbacks for supporting certificates #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Still need some additional events to hit
Setup so all of the callbacks should be there now.
Don't do bouncy castle RPK since not by default
Should be Certificate not AbstractCertificate
Get rid of mor RPK stuff that is not supported by default
Get all of the code to make server side notifications work Allow for an ipaddress to be used when starting the server rather than all
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Put in the necessary pointers so that we can support both raw public keys and certificates as part of our core code. Certificates are only supported via callbacks at this time while RPKs are supported both via the OneKey structure and RPKs. Also now have a callback for PSKs so that they can be dealt with as well if not known.
Addresses #46 and #32