tlshd/handshake: handle the UNKNOWN_PSK_IDENTITY alert#149
Merged
chucklever merged 1 commit intoMay 11, 2026
Conversation
During TLS handshake, an endpoint may issue an UNKNOWN_PSK_IDENTITY alert if it does not recognize the PSK identifier. For example, when using NVMe TCP in-band authentication with secure concatenation, if the target resets; the host kernel attempts to reconnect using a stale PSK, which the re-initialized target no longer recognizes. Map this specific TLS alert to EKEYREJECTED. This allows the kernel to identify that the failure is due to stale credentials, trigger key revocation, and proceed with fresh in-band authentication on the next reconnection attempt. Signed-off-by: Wilfred Mallawa <wilfred.mallawa@wdc.com>
Contributor
|
That looks good. Reviewed-by: Hannes Reinecke hare@kernel.org |
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
3 participants
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.
During TLS handshake, an endpoint may issue an UNKNOWN_PSK_IDENTITY alert if it does not recognize the PSK identifier. For example, when using NVMe TCP in-band authentication with secure concatenation, if the target resets; the host kernel attempts to reconnect using a stale PSK, which the re-initialized target no longer recognizes.
Map this specific TLS alert to EKEYREJECTED. This allows the kernel to identify that the failure is due to stale credentials, trigger key revocation, and proceed with fresh in-band authentication on the next reconnection attempt.