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

amber: 5/5 WARN on an AEC-reproduced artifact whose build environment is documented but not in a Dockerfile

Abierto
  • ¿Algo no está bien?
#535 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
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, python
Área
testing, tooling

Línea de trabajo

Start with entries/usenixsec2023-aeadprotocols.yaml in the amber-corpus repository and reproduce the audit on the #532 branch using the command in the issue. Then trace how the amber controls search for reproducibility evidence and handle the documented docker pull image. Done means the audit can distinguish missing evidence from evidence it cannot evaluate, and reports what it searched for.

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

Descripción

module-reproducibility

Summary

The five amber controls return WARN on an artifact that a USENIX Security '23 AEC independently reproduced, not because it lacks a reproducibility story, but because that story lives in the README and an external image rather than in files the controls look for.

git clone https://github.com/AutomatedAnalysisOf/AEADProtocols.git
cd AEADProtocols && git checkout V1 # cad164e
darnit audit --show-all --framework amber .

Total: 5 | Pass: 0 | Fail: 0 | Warn: 5 | N/A: 0 | Error: 0 | Pending LLM: 0
RE-01.01 .. RE-03.01: WARN - Could not automatically verify

No handler errors.

The artifact:

35 MB: Models/, README.md, tamarin-prover.zip. The README gives a pinned container and run command:

docker pull aeads/tamarin
docker run -it -v $PWD:/opt/case-studies aeads/tamarin bash

and vendors the prover source for manual builds. Badges: Available, Functional, Results Reproduced.

RE-01.02 (BuildEnvDeclared) is the clearest case, the build environment is declared, just not as a Dockerfile. And the WARN is indistinguishable from one on a repo with no evidence at all, which is the same complaint as #427.

Suggestions:

  1. Distinguish no candidate evidence found from candidates found but unevaluable, reporting what was searched for would be a start.
  2. Consider whether a documented docker pull <image> counts as a declared build environment, even at suggestive authority

From darnitdevorg/amber-corpus (#534) - artifacts with externally established expected outcomes, so a verdict can be judged right or wrong. Entry: entries/usenixsec2023-aeadprotocols.yaml. Run on the #532 branch.

Lenguaje dominante
Python
Estrellas
22
Forks
27
Merge medio
1 d 19 h
PR fusionados (30 d)
39

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 darnitdevorg/darnit

Todos los issues de darnitdevorg/darnit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.