Skip to content

chore(security): remove stale scripts/start-amc.sh (secrets + old path) - #14

Merged
SabaTech-dev merged 1 commit into
mainfrom
chore/remove-stale-start-amc
Aug 31, 2026
Merged

chore(security): remove stale scripts/start-amc.sh (secrets + old path)#14
SabaTech-dev merged 1 commit into
mainfrom
chore/remove-stale-start-amc

Conversation

@SabaTech-dev

Copy link
Copy Markdown
Owner

Por qué

scripts/start-amc.sh está stale y es un riesgo de higiene:

  1. cd a ruta vieja pre-migración (.openclaw/workspace/Alfred-Mission-Control) — si alguien lo ejecuta, arranca la app equivocada
  2. KANBAN_AGENT_KEYS (6 keys) y JWT_SECRET hardcodeados en plaintext — duplicados del EnvironmentFile /etc/alfred-mission-control.env que ya usa el unit

Evidencia

  • Cero referencias funcionales (solo .nft.json de build, que son file-traces)
  • El unit alfred-mission-control.service (activo) usa WorkingDirectory + EnvironmentFile correctos

Nota de seguridad

Los secrets permanecen en el historial git (commits antiguos) → rotación de JWT_SECRET/KANBAN keys a evaluar (decisión Joker/Alfred).

Ref: card f26fb6b6 · Backup: ~/backups/amc-start-amc-20260831/

- Apuntaba a ruta vieja pre-migracion (.openclaw/workspace/Alfred-Mission-Control)
- KANBAN_AGENT_KEYS y JWT_SECRET hardcodeados en plaintext (duplicados del
  EnvironmentFile /etc/alfred-mission-control.env que usa el unit real)
- Cero referencias funcionales (solo artefactos .nft.json de build)
- El unit alfred-mission-control.service (activo) gestiona el servicio real

Backup: ~/backups/amc-start-amc-20260831/
Nota: secrets en historial git -> rotacion a evaluar (Joker/Alfred)
Ref: card f26fb6b6
@SabaTech-dev
SabaTech-dev merged commit c56cbec into main Aug 31, 2026
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