Build the database, share and host settings packs

Abierto
#97 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
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
linux, mariadb, mysql, powershell, sql
Área
security

Línea de trabajo

Start on branch phase-7/service-packs-data in phases/harden/modules/pack_data/ per spec design 11 section 6. First read #80 and #89 to see existing pack structure, then build the MySQL/MariaDB, SQL Server, SMB, WinRM and vsftpd packs plus host settings library. Write bats and Pester acceptance tests; done means packs are idempotent and probes pass.

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

Descripción

area: services phase: harden platform: linux platform: windows type: build

Location & Context

Roadmap branch phase-7/service-packs-data. Spec: design 11 (including section 6). Planned module ID: harden.pack_data, in phases/harden/modules/pack_data/. Depends on #80 and #89.

Current Behavior

MySQL or MariaDB, SQL Server, SMB shares, WinRM and vsftpd are left at their defaults, and there is no host settings library.

Remediation Plan

  1. Build packs for MySQL or MariaDB, SQL Server, SMB shares, WinRM and vsftpd.
  2. Build the host settings library, including the pkexec setting (remove the setuid bit where no scored service uses it, recording the previous mode).
  3. Write these acceptance tests first (bats and Pester):
    • Each pack, run twice, changes nothing the second time.
    • With pkexec's setuid bit removed, an unprivileged lab user cannot run it as root, every probe passes, and rollback restores the bit.
    • On a version not listed as tested the pack applies nothing automatically.
    • Every automatic setting leaves the scoring-style probe passing.
    • A negative test: protected accounts and scored services are untouched before and after.
Lenguaje dominante
PowerShell
Estrellas
0
Forks
0
Merge medio
54 min
PR fusionados (30 d)
43

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 dotnetdork/Labyrinth

Todos los issues de dotnetdork/Labyrinth

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.