Skip to content

shred: should use all internal overwrite patterns in 25 passes #7809

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cakebaker opened this issue Apr 21, 2025 · 0 comments · Fixed by #7830
Closed

shred: should use all internal overwrite patterns in 25 passes #7809

cakebaker opened this issue Apr 21, 2025 · 0 comments · Fixed by #7830

Comments

@cakebaker
Copy link
Contributor

The documentation states:

After 25 passes all of the internal overwrite patterns will have been used at least once.

However, with our implementation this is not the case. For example, in the following example, the 111111, 666666 and cccccc patterns are missing:

$ cargo run -q shred -vn25 foo.txt
shred: foo.txt: pass 1/25 (random)...
shred: foo.txt: pass 2/25 (dddddd)...
shred: foo.txt: pass 3/25 (555555)...
shred: foo.txt: pass 4/25 (eeeeee)...
shred: foo.txt: pass 5/25 (000000)...
shred: foo.txt: pass 6/25 (222222)...
shred: foo.txt: pass 7/25 (random)...
shred: foo.txt: pass 8/25 (ffffff)...
shred: foo.txt: pass 9/25 (6db6db)...
shred: foo.txt: pass 10/25 (924924)...
shred: foo.txt: pass 11/25 (777777)...
shred: foo.txt: pass 12/25 (bbbbbb)...
shred: foo.txt: pass 13/25 (random)...
shred: foo.txt: pass 14/25 (333333)...
shred: foo.txt: pass 15/25 (492492)...
shred: foo.txt: pass 16/25 (999999)...
shred: foo.txt: pass 17/25 (888888)...
shred: foo.txt: pass 18/25 (aaaaaa)...
shred: foo.txt: pass 19/25 (random)...
shred: foo.txt: pass 20/25 (ffffff)...
shred: foo.txt: pass 21/25 (db6db6)...
shred: foo.txt: pass 22/25 (555555)...
shred: foo.txt: pass 23/25 (444444)...
shred: foo.txt: pass 24/25 (249249)...
shred: foo.txt: pass 25/25 (random)...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant