platform: sslmode=verify-full in a database URL fails as a generic configuration error
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
- 38/100
Línea de trabajo
Start in crates/registry-messaging/src/store.rs at PgConfig::from_str(url).map_err(|_| StoreError::Configuration) and confirm tokio-postgres 0.7.18's accepted sslmode values in Config::from_str. Before writing anything, check whether each runtime's TLS setup verifies both chain and host name, since that decides whether verify-ca/verify-full can be accepted or must be refused with a named error. The same parser appears in BReg, Casework, Scheduling, Document Store, the Adapter facade and job host; docs live in operate/breg.mdx and operate/coordinator.mdx. Done means one rule applied everywhere plus a verify-full test per product.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
A database URL with sslmode=verify-full fails as a generic configuration error. verify-full is the value the PostgreSQL documentation recommends, so operators will write it.
Observed with Messaging during the Stage 0 adopter run for #2745: messagingctl plan reported error[database.unavailable] ... configuration is invalid against a private CA. The same URL with sslmode=require and database.trustedRootCertificateRef worked.
Cause
tokio-postgres 0.7.18 accepts only disable, prefer and require for sslmode (Config::from_str). Any other value fails to parse, and the product maps the parse failure to its generic configuration error. In Messaging that is crates/registry-messaging/src/store.rs, PgConfig::from_str(url).map_err(|_| StoreError::Configuration).
The same parser reads the database URL in BReg, Casework, Scheduling, Document Store, the Adapter facade and the Adapter job host.
The runtimes already force TLS and verify the server certificate against the configured trust roots, whatever sslmode says.
Docs disagree
- operate/breg.mdx says the URL needs no
sslmodeparameter, because the runtime requires TLS itself. - operate/coordinator.mdx says to use
sslmode=require. - The other operate pages do not say which values they accept.
Proposal
- Pick one rule for every product. Either accept
verify-caandverify-full, since the runtime already verifies the certificate, or refuse them with an error that namessslmodeand the accepted values. Accepting them is the simpler adopter path, but only if the runtime's verification is at least whatverify-fullpromises (chain and host name). Check that before choosing. - Put one sentence about
sslmodeon every operate page that takes a database URL, using the same wording.
Both changes need a test per product that a verify-full URL gives the chosen result.
- Lenguaje dominante
- Rust
- Estrellas
- 2
- Forks
- 0
- Merge medio
- 9 h 48 min
- PR fusionados (30 d)
- 151
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de registrystack/registry-stack
-
area:breg enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
registrystack/registry-stack#2765 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
registrystack/registry-stack#2761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
registrystack/registry-stack#2743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
registrystack/registry-stack#2706 ·
Los mantenedores suelen responder en 1 día
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
registrystack/registry-stack#2704 ·
Los mantenedores suelen responder en 1 día
Todos los issues de registrystack/registry-stack
Issues similares
-
[Bug] 建议把黑白主题设置同步到启动页面Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
stackabletech/airflow-operator#898 ·
Los mantenedores suelen responder en 1 día
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Posiblemente ocupada @zyl71 la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100