feat(protocol): add PSK authentication provider - #32
Merged
Conversation
This file contains hidden or 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
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.
Merge order
CertificateAuthrefactorPskAuthThis branch is stacked directly on exact #31 head
8fb37ca. Please merge #31 first; this PR's independent change is commit2a6fc62. I will rebase or restack it after #31 if the merge method requires that.Summary
PskAuthfor an existing raw OCF identity and PSKbytesinputs, a 16-byte NUL-free identity, and a 16- or 32-byte keyECDHE-PSK-AES128-CBC-SHA256, with no certificate-suite fallback or global OpenSSL changeScope boundary
This is the pure
PskAuthslice agreed in #28. It consumes a credential that the caller already holds.It does not derive, discover, acquire, persist, rotate, provision, or write credentials; perform ownership transfer or OTM; access Samsung cloud/account services; add certificate server profiles; or change session lifecycle behavior.
Consequently, it does not by itself solve #16 or #20. The former still needs an authorized identity and later opt-in profile support; the latter requires credential acquisition/vendor OTM outside this package.
Validation
Part of #28.