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

UX: /etc/sudeoers.d/myrules.conf doesn't work - allow dots or help users along the way

Abierto
  • ¿Algo no está bien?
#486 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c
Área
cli

Línea de trabajo

Start by reading the sudoers manual section on files in sudoers.d, then trace how sudo selects and skips files in that directory; the issue does not name source files or tests. The report suggests several possible UX changes, including accepting .conf files, adding guidance, or warning interactively, so first identify the existing behavior and tests before assessing scope. Done means an agreed change helps users understand why a dotted file is ignored.

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

Descripción

In my experience the drop in directories like /etc/ssh/ssh_config.d/ for example need a .conf file extension to actually take effect. For sudo the contrary seems to be the case: The file is silently ignored if it contains a dot which of course is true for my file ending in .conf.

In an ideal world there would be a standard for stuff like that so that users like me wouldn't need to remember or figure it out as they are using a myriad of different tools. On the other hand I realize that changing that behavior now for sudo might be problematic for all the systems already depending on that behavior, as much as I'd like to see it unified. (But maybe allowing just .conf wouldn't be too bad? The Documentation just mentions that dotted files are skipped to avoid issues with package managers but I don't think any of them would be writing .conf files there...)

What else could be done to improve the UX?

  • Put a readme.txt or a example file in sudoers.d which educates about this circumstance, this is the first place I have looked but the directory was empty for me. (Fedora 43 after many upgrades.)
  • I've briefly looked into man sudoers but didn't really think about where to look specifically. Only later I found that the information is actually there hidden somewhere in the middle of of over 2000 lines. (A search engine and stackoverflow came to the rescue.)
  • I've tried sudo -v and looked into man sudo for a verbose mode (which is helpful in debugging ssh client issues) and also tried sudo -l but neither helped me figure out why my new .conf file was doing nothing.
  • At least when running interactively (like asking for a password) I don't see any harm in announcing that a dotted file in sudoers.d was skipped because of the dot.

Finally a big thank you to all the people creating and maintaining sudo! ❤️
(Apart from this minor annoyance in the config it never let me down 😉 )

In retrospect the title for this issue feels a bit clunky, feel free to edit or suggest improvements if you got better ideas.

Lenguaje dominante
C
Estrellas
1.7k
Forks
306
Merge medio
1 d 2 h
PR fusionados (30 d)
22

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 sudo-project/sudo

Todos los issues de sudo-project/sudo

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.