Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Reports should say what the user attempted

未关闭
#378 3 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
c
领域
cli

调研方向

Read the sudoers reporting code that produces the shown “user NOT in sudoers” message and locate its tests; the payload names no files or tests, so first search the repository for that text. Check how the attempted command and authentication outcome are represented, then update the report wording and formatting to make the event clear and fit on one screen. Done when tests cover the revised report.

由索引模型根据 Issue 内容生成。

描述

This lacks one critical detail,

From: Dan Jacobson <[email protected]>
Subject: *** SECURITY information for jidanni5.jidanni.org ***
To: [email protected]
Date: Mon, 20 May 2024 18:19:32 +0800

jidanni5.jidanni.org : May 20 18:19:32 : jidanni : user NOT in sudoers ; TTY=pts/0 ; PWD=/home/jidanni ; USER=root ; COMMAND=/usr/bin/w

i.e., what did the user do?

It should say that "user attempted run the command "w" using sudo, and entered a password, but then was discovered not to be on the sudoers list.

I mean one day one of these reports will end up in a court of law, so what happened needs to be real clear! Even if it was just little old me testing sudo.

Might as well also fold it to fit on one screen.

And maybe remove the blanks before the semicolons, as in English.

主要语言
C
星标
1.7k
派生
306
平均合并
1 天 8 小时
30 天内合并 PR
24

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

sudo-project/sudo 的其他 Issue

查看 sudo-project/sudo 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。