fix: require verified production email
CI and Deploy / test (pull_request) Successful in 4m42s
CI and Deploy / deploy (pull_request) Has been skipped
CI and Deploy / test (push) Successful in 4m2s
CI and Deploy / deploy (push) Failing after 1m15s

Expose the existing email-verification setting through Compose and close the completed DataProtection rotation blocker.
This commit is contained in:
cesnimda
2026-08-02 17:59:05 +02:00
parent 955182b7c2
commit 06518a7d52
7 changed files with 13 additions and 17 deletions
+1 -1
View File
@@ -386,7 +386,7 @@ Compose bounds each container's local logs to three 10 MB files. There is still
| Sev | Finding | Status |
|---|---|---|
| Medium | DataProtection keys recoverable from git history (`519c32e`, `955cae6`) | **Open — rotation required, needs an operator** |
| Medium | DataProtection keys recoverable from git history (`519c32e`, `955cae6`) | **Closed 2026-08-02production keys rotated by the operator** |
| Medium | Wildcard credentialed CORS configuration | **Closed — startup rejects it** |
| Medium | AI cost ceiling | **Closed — monthly generation/token limits are enforced by plan** |
| Low | Public-registration abuse control | Implemented with Turnstile; production keys/configuration still required |