Skip to content

fix: remove vendor encryption key, close proxy-set path, tighten DCO gate - #3

Merged
Vonng merged 1 commit into
mainfrom
fix/rebrand-followup
Aug 6, 2026
Merged

fix: remove vendor encryption key, close proxy-set path, tighten DCO gate#3
Vonng merged 1 commit into
mainfrom
fix/rebrand-followup

Conversation

@Vonng

@Vonng Vonng commented Aug 6, 2026

Copy link
Copy Markdown
Member

Follow-up to the rebranding review (PR #2). Addresses the three P1 findings plus the minor items.

P1

Vendor encryption key removed. support inspect fell back to MinIO's support public key when the operator had not supplied one (cmd/support-inspect.go), so locally saved raw object data was encrypted to a key only MinIO holds — neither local nor recoverable by the operator who produced it. Now: an operator-supplied support_public.pem still takes precedence; without one, madmin's no-key path has the server generate a key and return it to the caller, who is its only holder (this is the path --legacy already used, and the key is printed once). The encrypted upload path in cmd/subnet-file-uploader.go fails closed rather than reaching for a vendor key, and the key blob no longer exists anywhere in the binary.

support proxy set closed. It wrote subnet proxy=… to the target server — configuring its outbound path to SUBNET. Now exits with the stable disabled error, consistent with callhome enable. show and remove keep working so operators can inspect and clear a legacy setting.

DCO exemption tightened. The bot exemption keyed on the display name, which any author can set; it now requires a GitHub-issued bot address (*[bot]@users.noreply.github.com).

Minor

  • source builds printed Copyright (c) 2025-0000 PGSTY; the 0000 placeholder now falls back to the current year (release ldflags path unchanged)
  • 6 pre-existing whitespace errors (trailing space / space-before-tab in upstream help templates) surfaced by the brand sweep
  • PR template section renamed from "Community Contribution License" to match the no-CLA policy
  • CONTRIBUTING: assistive-tooling trailers (e.g. Co-Authored-By: naming an AI) are informational only — no authorship, no copyright claim; the human signatory remains responsible

Regression coverage

  • TestEncryptedUploadRequiresAnExplicitKey — encrypted upload with no configured key must fail closed
  • brand gate rejects any embedded public key blob in cmd/

Verification

go build ./..., go vet ./..., make lint (0 issues), go test ./... -count=1 all green; git diff --check clean. Smoke: support proxy set exits 1 with the disabled error, support proxy remove unaffected, --version shows 2025-2026 PGSTY in a source build.

Not addressed here (needs owner action)

Branch protection on main — no ruleset exists, which is why PR #2 could be merged before checks finished. Recommend requiring a PR plus the Go, vetchecks, DCO and Analysis checks. Separately, the migration manual's Phase 0 legal review of the Silo/mcli naming and trademark wording remains outstanding and cannot be satisfied by code or CI.

🤖 Generated with Claude Code

Follow-up to the rebranding review.

- support inspect no longer falls back to MinIO's support public key when
  the operator has not supplied one. That fallback encrypted locally
  saved object data to a key only MinIO holds, so the output was neither
  local nor recoverable by the operator who produced it. Without a key,
  the server generates one and returns it to the caller, who is its only
  holder; an operator-supplied support_public.pem still takes precedence.
  The encrypted upload path fails closed instead of reaching for a vendor
  key, and the key blob is gone from the binary entirely.
- support proxy set configured the server's outbound path to SUBNET, so
  it now exits with the stable disabled error; show and remove keep
  working so operators can inspect and clear a legacy setting.
- the DCO exemption keyed on the display name, which any author can
  choose; it now requires a GitHub-issued bot address.
- source builds printed 'Copyright (c) 2025-0000 PGSTY'; the placeholder
  now falls back to the current year, with release ldflags unchanged.
- PR template section renamed to match the no-CLA policy, and
  CONTRIBUTING states that assistive-tooling trailers carry no authorship
  or copyright and that the human signatory remains responsible.
- fixed 6 pre-existing whitespace errors surfaced by the brand sweep.

Regression coverage: fail-closed encryption test, plus a brand-gate rule
rejecting any embedded public key in cmd/.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: Feng Ruohang <rh@vonng.com>
@Vonng
Vonng merged commit d2c0db7 into main Aug 6, 2026
7 checks passed
@Vonng
Vonng deleted the fix/rebrand-followup branch August 6, 2026 04:16
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.

1 participant