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

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

Aberta
  • Algo errado?
#486 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
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
c
Domínio
cli

Direção de pesquisa

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.

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

Descrição

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.

Linguagem predominante
C
Estrelas
1.7k
Forks
306
Merge médio
1d 2h
PRs com merge (30d)
22

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

Todas as issues de sudo-project/sudo

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

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