trifectatechfoundation / trifectatechfoundation/sudo-rs

Fingerprinting problems

Open
#1,609 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted
Dominant language
Rust
Stars
4.5k
Forks
179
Avg merge
16h 45m
Merged PRs (30d)
4

Description

Describe the bug
I'm using sudo rs for while and I'm having some issues with fingerprinting

I'm using it in NixOS (master branch of nixpkgs)
And I have two problems and one recommendation

  1. When scanning/waiting for fingerprint, Control-C will not work and I have to force kill (-9) or use Control-Z
  2. When sudo-rs crashes (specially in the middle of the scan), fingerprinting will not work until I restart
  3. For things like fingerprinting it should use a master process that others reuse the same fingerprint connection or session

To Reproduce
Steps to reproduce the behavior:

  1. Install 'sudo-rs'
  2. See error (See 3 items on top)

Expected behavior
Clean exit

Environment (please complete the following information):

  • Linux distribution: NixOS (master branch)
  • sudo-rs version [sudo --version] or commit hash: 0.2.13

Additional context
Add any other context about the problem here.

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the fingerprint scan behavior described for sudo-rs 0.2.13 on NixOS, focusing on Ctrl-C handling and what remains after a crash. Trace the fingerprinting process and cleanup path; done means interruption exits cleanly and a subsequent scan works without restarting, while the proposed shared session remains to be evaluated.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, operating-systems, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.