Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

More discrete alternative to pwfeedback

Open
#536 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
46/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c
Domain
cli

Research direction

Start by reading how sudo currently handles password input and echo-off feedback; the issue does not name files, tests, or entry points, so locate that code in the repository first. Compare the proposed single changing character with the current feedback behavior. Done means the feedback avoids revealing password length and gives a blank prompt after Backspace deletes the final character.

Written by the indexing model from the issue text.

Description

As an alternative to sequential asterisks (******) that are easier for others to count, what if we had something similar to e.g. swaylock:

Screenshot of swaylock

Sway uses a circle that changes randomly as you type or delete characters.

When all characters have been deleted, it displays a "Cleared" message.

Screenshot of swaylock with Cleared message

Since sudo is a command-line program, maybe we could "spin" a character:

|
/
—
\
|

Or display one random character for every keypress.

#
!
(
5
~
`
e

(to be clear: only one character would be displayed at a time)

To me, the most confusing aspect of "echo off" appears when I make a typo and have to hold Backspace to delete everything and start over. There is no "cleared" feedback to let you know when you've deleted the last character. To indicate such event on the command-line, I would delete/hide the feedback character, leaving the prompt blank until the first character is typed.

Dominant language
C
Stars
1.7k
Forks
306
Avg merge
1d 8h
Merged PRs (30d)
24

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sudo-project/sudo

All issues in sudo-project/sudo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.