Secret settings are stored in plaintext

Abierto
#3,270 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend, security

Línea de trabajo

Start with SettingsService.StoreAsync and the code that resolves settings, especially handling of [SettingsSecret] values such as AiSettings.ApiKey. Trace how the startup report is built and how settings are written to cms_setting.json; the proposal specifies the protection purpose and when existing values should be migrated. Done means stored secrets are protected, existing plaintext values still resolve and become protected on their next write, and unprotected secrets are reported at startup.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:settings security type:bug

Problem

[SettingsSecret] values such as AiSettings.ApiKey are written as is to cms_setting.json (SettingsService.StoreAsync); only Management API reads redact them. A database reader, a backup or a replica gets third-party API keys, even on a host with a certificate-protected key ring.

Proposal

Protect secrets with IDataProtector (purpose settings:{area}:{key}) on write and unprotect on resolve; report unprotected secrets in the startup report; migrate existing values on first write.

Acceptance

  • A secret setting is not readable from the database
  • Existing plaintext values keep working and are protected on their next write

Found in the code review of 17 Nov 2026 (S4).

Lenguaje dominante
C#
Estrellas
569
Forks
107
Merge medio
2 h 49 min
PR fusionados (30 d)
397

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.