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

attachments: strip EXIF metadata from image attachments

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

Línea de trabajo

Start by locating IncidentFile's add path and tracing how image bytes are stored and passed to sync and PDF generation. Check existing image-processing dependencies and tests; the issue gives no specific test file. Done means metadata is stripped on ingest across supported image formats while orientation is preserved, and merged PDF metadata remains out of scope unless inexpensive.

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

Descripción

enhancement help wanted

What

Lagebuch does not strip EXIF metadata from attached images. A repo-wide search for exif over src/ returns nothing; image bytes go into the .files folder verbatim and into the PDF report verbatim.

Why it matters

A photo taken with a Diensthandy at the Einsatzstelle typically carries GPS coordinates, the exact capture timestamp, and the device model. All of that travels with the attachment: into the incident's .files folder, over the sync connection to every joined device, and into the exported PDF that goes to the Akte and the Kreisbrandinspektion.

The coordinates are usually the address of a private property, and often the address of the person whose name is already in the CO-Messprotokoll. Nothing about the app's UI suggests a photo carries anything beyond what is visible in it.

docs/datenschutz-und-sicherheit.md (#380) names this as a known limit, which is the honest short-term answer, but stripping is the right one.

Shape

Strip on ingest, in IncidentFile's add path, so it applies uniformly to the local store, the sync payload and the PDF — rather than at export, which would leave the stored copy untouched.

Decide deliberately what to keep: orientation must survive or photos display rotated. Everything else (GPS, timestamps, device, serial numbers, thumbnails — which can themselves contain a pre-edit image) can go.

PNG/WebP/GIF carry metadata chunks too and should be handled in the same pass. Merged PDF attachments have their own metadata; out of scope here unless it is cheap.

Lenguaje dominante
C#
Estrellas
1
Forks
3
Merge medio
4 h 49 min
PR fusionados (30 d)
177

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 CodeForFire/lagebuch

Todos los issues de CodeForFire/lagebuch

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.