Skip to content

fix: TLS off-loopback; S3 NFR is rsync (0.3.1) - #2

Open
RichardHightower wants to merge 1 commit into
mainfrom
rev4/tls-and-s3-nfr
Open

fix: TLS off-loopback; S3 NFR is rsync (0.3.1)#2
RichardHightower wants to merge 1 commit into
mainfrom
rev4/tls-and-s3-nfr

Conversation

@RichardHightower

Copy link
Copy Markdown
Contributor

Addresses the 0.3.0 review on okf-plugin#74. Spec comments landed first.

TLS

Loopback (127.0.0.1, ::1, localhost) may bind bare. Any other bind requires OKF_MCP_TLS_CERT + OKF_MCP_TLS_KEY or it is a startup error — same shape as the issuer check. 0.0.0.0:8080 without certs will not start.

S3 latency

The low-latency NFR holds for rsync push. S3 end-to-end is still bounded by the consumer daemon's pull. Bucket notifications are a different transport and are not picked. docs/S3.md says so.

19 tests green. Version 0.3.1.

Non-loopback --bind without OKF_MCP_TLS_CERT/KEY is a startup error.
Loopback may still bind bare. Low-latency NFR holds for rsync push; S3
end-to-end stays bounded by the consumer daemon's pull.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants