Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Adversarial audit of the remote-control model by a model not used in development

Cerrado
  • ¿Algo no está bien?
#1,194 2 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend, documentation, security

Línea de trabajo

Read docs/specs/security-audit.md and the threat model sections named in the issue, then inspect remote-lib-common/src/security/ and the Hosted Relay, rendezvous, and account boundaries. Run an independent adversarial review without using the existing FAIL IF lines as prompts. Done means recording each finding and disposition, and documenting whether and how often the audit repeats.

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

Descripción

security

The nightly audit (docs/specs/security-audit.md) checks every FAIL IF line in the domain specs, and the canary recall measures how often it catches a planted break. But the same model family wrote the specs, the code, and the audit prompts. A blind spot shared by all three would pass every night.

This issue tracks one independent, adversarial pass over the remote-control model, run by a model family that has not been used to develop or review Dormouse.

Scope

The parts where an end-to-end break would be silent:

  • the Noise integration (remote-lib-common/src/security/), and its one-channel-per-ceremony rule (docs/specs/remote-security-model.md -> "Trust Model");
  • the WebAuthn presence binding inside that channel;
  • key storage at both ends (docs/specs/security-remote.md -> "Credentials at rest");
  • the push construction (docs/specs/remote-security-model.md -> "Push sealing");
  • Hosted's Relay, rendezvous, and account boundaries (docs/specs/security-hosted.md).

Approach

  • Give it the code and the threat model, not our FAIL IF lines. The point is to find what our checks never ask.
  • Ask for concrete attacks against each guarantee on /security, each with a reproduction or a reason it fails.
  • Every finding either becomes a fix, a new FAIL IF line with a canary seed, or an entry under "What is not defended" or "Known gaps".

Done when

  • The pass has run, and its findings and their dispositions are recorded here.
  • docs/specs/security-audit.md says whether this repeats, and how often.
Lenguaje dominante
TypeScript
Estrellas
5
Forks
1
Merge medio
10 h 51 min
PR fusionados (30 d)
507

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 diffplug/dormouse

Todos los issues de diffplug/dormouse

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.