Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#1,194 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
18/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
backend, documentation, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
TypeScript
Estrelas
5
Forks
1
Merge médio
10h 50min
PRs com merge (30d)
494

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de diffplug/dormouse

Todas as issues de diffplug/dormouse

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.