docs(tls): document multi-source cipher/SECLEVEL resolution per listener#598
Open
heskew wants to merge 2 commits into
Open
docs(tls): document multi-source cipher/SECLEVEL resolution per listener#598heskew wants to merge 2 commits into
heskew wants to merge 2 commits into
Conversation
Documents HarperFast/harper#1841 (5.2.0): every configured ciphers source is honored — composed as suites-from-highest-priority-source plus the minimum explicit @SECLEVEL — with CA entries scoped to mTLS-verifying listeners, operationsApi.tls precedence, composition warnings, and the restart-required caveat for post-boot changes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
🚀 Preview DeploymentYour preview deployment is ready! 🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-598 This preview will update automatically when you push new commits. |
heskew
marked this pull request as ready for review
July 20, 2026 16:55
kriszyp
requested changes
Jul 20, 2026
…A-1 chain wording, Node-path scoping, entry relevance Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
🚀 Preview DeploymentYour preview deployment is ready! 🔗 Preview URL: https://preview.harper-documentation.harperfabric.com/pr-598 This preview will update automatically when you push new commits. |
kriszyp
approved these changes
Jul 23, 2026
kriszyp
left a comment
kriszyp
left a comment
Member
There was a problem hiding this comment.
- Documents Harper 5.2's listener-wide Node/OpenSSL cipher and
@SECLEVELresolution. - Explains source relevance and priority, minimum-level composition, and the restart warning for later certificate changes.
- The follow-up commit correctly scopes the behavior away from Bun and tightens the SHA-1 and listener-wide security wording.
- No correctness, clarity, or formatting problems found.
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
2 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.
Summary
Documents the composed per-listener cipher resolution shipped in HarperFast/harper#1841 (v5.2.0, closes harper#1840):
tls.ciphersfield description updated: the value may live at the top level, ontls[]entries, or on certificate records, and is composed per listener.reference/http/tls.md: source priority (operationsApi.tls> roottls> certificate records), relevance rules (CA entries only for mTLS-verifying listeners;usesmatching incl. legacyhttps/no-usesgenerics), suite-preserving@SECLEVELcomposition with a worked legacy-client-CA example, composition warnings, and the restart-required caveat for post-boot changes.<VersionBadge type="changed" version="v5.2.0" />.Where to look
HIGH:!aNULL+ CADEFAULT@SECLEVEL=0toHIGH:!aNULL@SECLEVEL=0— matches the resolver's unit tests in core.🤖 Generated with Claude Code (Claude Fable 5)