settings reprotect: name the default key, report values it cannot reach, and settle rows of unregistered areas

Abierto
#3,436 1 comentario 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
54/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start with the fluentcms settings reprotect implementation and its tests, then read the related behavior in #3364 and #3433. The issue also points to docs/host-configuration.md; inspect how settings areas and cached key rings are handled before choosing the unregistered-area cleanup behavior. Done means the output names the default key id, unreachable protected values are reported without revealing values, the cleanup path is decided and documented, and tests cover the command changes.

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

Descripción

area:settings type:bug

Follow-ups of fluentcms settings reprotect (#3364, #3433), found in its review. None loses or shows a secret.

  • The command does not say which ring key it protected under. It ends with exit code 0 whatever the default key is. Run before the key that is to be kept has become the default, it succeeds, and retiring the old key afterwards still loses the secrets. Name the id of the default key in the output; the id is not secret.
  • Protected values the pass cannot reach in a registered area are skipped without a word. A fcms-protected:v1: value under a key the class no longer has, or no longer marks as a secret, is left as it is and the command ends with 0. Rows of an area no class registers are reported; these are not.
  • No way to remove the settings rows of an area no class registers. A host that removed a plugin with secret settings gets exit code 1 from every run, and neither the API nor reset knows the area.
  • The docs do not say when an instance may still write under the old key. A running instance caches the ring for up to 24 hours, so with a key made by hand it can protect a write under the old default after the pass. Say when to run the pass, or that the instances are restarted first.

Wanted

  • The default key's id in the command's output, with a test.
  • Such values reported by area and scope, never by value, with a test.
  • A decision on the rows of an unregistered area: a command or an option that removes them, or the documented way to do it.
  • The sentence in docs/host-configuration.md.

Found in the review of #3433. Bundle 25.

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

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.