Hash operations should leave some feedback on progress
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
**Is your feature request related to a problem? Please describe.**
I have a couple of large ISO files and kernels in my `/boot`. Many Heads operations (re-signing, looking for boot options) take a long time. Usually the systems seems stuck after printing `*** Found verified kexec boot params` or `Veryfing presence of GPG card...`.
This led me to incorrect assumptions few times - I have suspected that something is wrong with smartcard operations, for example.
**Describe the solution you'd like**
Maybe sha256sum operation should print what it is doing (like giving the file name of the file being hashed).
**Describe alternatives you've considered**
No alternatives have been considered.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the Heads code for the messages `*** Found verified kexec boot params`, `Veryfing presence of GPG card...`, and its sha256sum invocations to identify the affected operations. The change is done when long-running hash operations visibly identify the file or work in progress instead of appearing stuck.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100