GovOPlaN/govoplan-campaign
1
0
Fork 0
Code Issues 46 Pull Requests Actions Packages Projects Releases Wiki Activity

[Security] Retire legacy inline Campaign mail secrets from history and backups #77

New Issue
Closed
opened 2026-07-21 16:57:19 +02:00 by zemion · 1 comment
zemion commented 2026-07-21 16:57:19 +02:00
Owner
Copy Link

Outcome

No live Campaign row, generated runtime artifact, retained execution snapshot, or eventually expired backup remains a reusable SMTP/IMAP credential store. The remediation remains attributable without copying or hashing password values into new evidence.

Current containment

New authoring accepts only server.mail_profile_id. Legacy inline transport records are recursively redacted from ordinary responses and fail closed for validation/build/queue/retry/delivery. This prevents execution and disclosure but deliberately does not remove historical plaintext at rest.

Decision required

Changing locked/versioned source JSON is a security remediation that conflicts with byte-for-byte historical immutability. Approve the evidence model and backup treatment before implementation:

  • Live rows: remove secret-bearing fields (and preferably all consumer-owned transport copies), record affected version/snapshot ids and removed field classes/counts in a non-secret audit event, and preserve no password-derived hash.
  • Runtime artifacts: identify and securely remove obsolete snapshot/generated-message directories according to Campaign evidence policy.
  • Backups: choose expiry/destruction or cryptographic-erasure/key-rotation treatment; an online migration cannot rewrite every retained copy safely.
  • Restoration: require a post-restore remediation gate before outbound delivery is enabled.

Acceptance after decision

  • A dry-run inventory reports counts and locations without values.
  • The migration is resumable, idempotent, tenant-scoped where practical, and separately authorized.
  • Locked/history records retain business content and a verifiable remediation marker while secret/config copies are removed.
  • Audit failure rolls back the corresponding live-row change.
  • Backups and runtime artifacts have an operator-approved treatment and restoration gate.
  • Regression scans seed distinctive plaintext/ciphertext values and prove they are absent from live Campaign persistence, exports, logs, reports, and retired artifacts.
## Outcome No live Campaign row, generated runtime artifact, retained execution snapshot, or eventually expired backup remains a reusable SMTP/IMAP credential store. The remediation remains attributable without copying or hashing password values into new evidence. ## Current containment New authoring accepts only `server.mail_profile_id`. Legacy inline transport records are recursively redacted from ordinary responses and fail closed for validation/build/queue/retry/delivery. This prevents execution and disclosure but deliberately does not remove historical plaintext at rest. ## Decision required Changing locked/versioned source JSON is a security remediation that conflicts with byte-for-byte historical immutability. Approve the evidence model and backup treatment before implementation: - Live rows: remove secret-bearing fields (and preferably all consumer-owned transport copies), record affected version/snapshot ids and removed field classes/counts in a non-secret audit event, and preserve no password-derived hash. - Runtime artifacts: identify and securely remove obsolete snapshot/generated-message directories according to Campaign evidence policy. - Backups: choose expiry/destruction or cryptographic-erasure/key-rotation treatment; an online migration cannot rewrite every retained copy safely. - Restoration: require a post-restore remediation gate before outbound delivery is enabled. ## Acceptance after decision - A dry-run inventory reports counts and locations without values. - The migration is resumable, idempotent, tenant-scoped where practical, and separately authorized. - Locked/history records retain business content and a verifiable remediation marker while secret/config copies are removed. - Audit failure rolls back the corresponding live-row change. - Backups and runtime artifacts have an operator-approved treatment and restoration gate. - Regression scans seed distinctive plaintext/ciphertext values and prove they are absent from live Campaign persistence, exports, logs, reports, and retired artifacts.
zemion commented 2026-07-21 20:00:09 +02:00
Author
Owner
Copy Link

Decision recorded 2026-07-21: there is no separate historical Campaign JSON corpus outside the current database. Inline SMTP/IMAP material in existing database rows remains inert, omitted from ordinary responses, and fail-closed for validation/build/queue/delivery. Normal database backup/restore and access controls cover those rows; GovOPlaN will not create a separate backup-scanning or historical-inline-secret remediation program. The handbook and Mail profile boundary have been updated accordingly, so this issue is closed as no longer required.

Decision recorded 2026-07-21: there is no separate historical Campaign JSON corpus outside the current database. Inline SMTP/IMAP material in existing database rows remains inert, omitted from ordinary responses, and fail-closed for validation/build/queue/delivery. Normal database backup/restore and access controls cover those rows; GovOPlaN will not create a separate backup-scanning or historical-inline-secret remediation program. The handbook and Mail profile boundary have been updated accordingly, so this issue is closed as no longer required.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
area/auth
Authentication, sessions, access bootstrap, or login behavior.
area/db
Database sessions, models, transactions, or persistence primitives.
area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
area/docs
Durable documentation and project guidance.
area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
area/marketing
Public website, product messaging, publication copy, or legal page content.
area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
area/rbac
Permissions, roles, delegation, or authorization policy.
area/release
Versioning, release locks, tags, packaging, or dependency pins.
area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
audit/quick-fix
Audit finding that appears narrow and directly fixable.
audit/structural
Audit finding that needs design, refactoring, or behavior review.
codex/needs-human
Needs an explicit human decision before Codex should implement.
codex/ready
Suitable for Codex to pick up with the existing issue context.
module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
module/addresses
GovOPlaN Addresses module behavior or integration.
module/admin
GovOPlaN Admin module behavior or integration.
module/appointments
GovOPlaN Appointments module behavior or integration.
module/audit
GovOPlaN Audit module behavior or integration.
module/calendar
GovOPlaN Calendar module behavior or integration.
module/campaign
GovOPlaN campaign module behavior or integration.
module/cases
GovOPlaN Cases module behavior or integration.
module/connectors
GovOPlaN Connectors module behavior or integration.
module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
module/dataflow
GovOPlaN Dataflow module behavior or integration.
module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
module/dms
GovOPlaN Dms module behavior or integration.
module/erp
GovOPlaN Erp module behavior or integration.
module/evaluation
GovOPlaN Evaluation module behavior or integration.
module/files
GovOPlaN files module behavior or integration.
module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
module/forms
GovOPlaN Forms module behavior or integration.
module/identity
GovOPlaN Identity module behavior or integration.
module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
module/idm
GovOPlaN Idm module behavior or integration.
module/ledger
GovOPlaN Ledger module behavior or integration.
module/mail
GovOPlaN mail module behavior or integration.
module/notifications
GovOPlaN Notifications module behavior or integration.
module/ops
GovOPlaN Ops module behavior or integration.
module/organizations
GovOPlaN Organizations module behavior or integration.
module/payments
GovOPlaN Payments module behavior or integration.
module/permits
GovOPlaN Permits module behavior or integration.
module/policy
GovOPlaN Policy module behavior or integration.
module/poll
GovOPlaN Poll module behavior or integration.
module/portal
GovOPlaN Portal module behavior or integration.
module/postbox
GovOPlaN Postbox module behavior or integration.
module/reporting
GovOPlaN Reporting module behavior or integration.
module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
module/scheduling
GovOPlaN Scheduling module behavior or integration.
module/search
GovOPlaN Search module behavior or integration.
module/tasks
GovOPlaN Tasks module behavior or integration.
module/templates
GovOPlaN Templates module behavior or integration.
module/tenancy
GovOPlaN Tenancy module behavior or integration.
module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
module/workflow
GovOPlaN Workflow module behavior or integration.
module/xoev
GovOPlaN Xoev module behavior or integration.
module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
source/security-audit
Created from a structured security or code-quality audit report.
source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
zemion
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-campaign#77
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?