Repository navigation
ohttp: add an AEAD suite policy for ingress and egress - #310
Merged
Merged
Conversation
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
imlk0
force-pushed
the
ohttp-aead-suite-policy
branch
from
November 5, 2026 07:07
675c5b5 to
663b390
Compare
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
imlk0
force-pushed
the
ohttp-aead-suite-policy
branch
from
November 5, 2026 07:11
663b390 to
90a5284
Compare
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
imlk0
force-pushed
the
ohttp-aead-suite-policy
branch
from
November 5, 2026 08:00
90a5284 to
13f8887
Compare
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
The fork's tng branch now carries AES-256-GCM in both HPKE backends and the explicit-suite constructors the ingress policy uses. The pin also picks up d2c5e38, which was already on the branch. Assisted-by: Claude:fable-5
Add an ordered ohttp.aead_suites allowlist. On the egress it drives both the advertised key config and the decapsulation allowlist. A disallowed suite returns HTTP 422 so a TNG ingress refetches its key config, and the check also covers keys issued before a policy change and keys synced from a peer_shared peer. On the ingress the list is an allowlist and a client preference order. The ingress picks the first server key config with an intersection, then the first suite in its own order. The selected config drives the metadata hint and the status public key. No intersection fails the key fetch, with no fallback. Not setting the field keeps the previous behavior. Include AES-256-GCM in both ohttp HPKE backends, unit and integration tests, and the configuration and changelog documentation. Assisted-by: Claude:fable-5
Both rules come from the OHTTP AEAD suite policy review. A name must match the value space it selects, and an invariant belongs to the type that owns it rather than to a global config pass. Assisted-by: Claude:fable-5
imlk0
force-pushed
the
ohttp-aead-suite-policy
branch
from
November 5, 2026 09:01
13f8887 to
0f97f74
Compare
|
@imlk0 ，您好，您的请求已接收，请耐心等待结果。 |
|
@imlk0 ，您好，未检测到有镜像需要构建，如需重新检测请评论 /start 。 |
This branch was previously deployed
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.
Adds
ohttp.aead_suites, an ordered HPKE AEAD allowlist on both sides.peer_sharedpeer.cargo build --lockedandmake clippypass locally; CI runs the tests.