-
Notifications
You must be signed in to change notification settings - Fork 9
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
Fault injection with fake storage capacity #62
Labels
Comments
ligurio
added a commit
that referenced
this issue
Aug 11, 2021
`errinj_wrong_capacity` reports a wrong storage capacity. There are many fraudulent USB sticks in circulation that report to have a high capacity (ex: 8GB) but are really only capable of storing a much smaller amount (ex: 1GB). Attempts to write on these devices will often result in unrelated files being overwritten. Any use of a fraudulent flash memory device can easily lead to database corruption, therefore. 1. https://www.sqlite.org/howtocorrupt.html Closes #62
ligurio
added a commit
that referenced
this issue
Jan 24, 2022
With error injection `errinj_wrong_capacity` filesystem reports a wrong storage capacity. Problem simulated with `errinj_wrong_capacity` may happen in real. For instance see a case described in SQLite documentation: "There are many fraudulent USB sticks in circulation that report to have a high capacity (ex: 8GB) but are really only capable of storing a much smaller amount (ex: 1GB). Attempts to write on these devices will often result in unrelated files being overwritten. Any use of a fraudulent flash memory device can easily lead to database corruption, therefore." 1. https://www.sqlite.org/howtocorrupt.html Closes #62
ligurio
added a commit
that referenced
this issue
Jan 24, 2022
With error injection `errinj_wrong_capacity` filesystem reports a wrong storage capacity. Problem simulated with `errinj_wrong_capacity` may happen in real. For instance see a case described in SQLite documentation: "There are many fraudulent USB sticks in circulation that report to have a high capacity (ex: 8GB) but are really only capable of storing a much smaller amount (ex: 1GB). Attempts to write on these devices will often result in unrelated files being overwritten. Any use of a fraudulent flash memory device can easily lead to database corruption, therefore." 1. https://www.sqlite.org/howtocorrupt.html Closes #62 wrong
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://www.sqlite.org/howtocorrupt.html
The text was updated successfully, but these errors were encountered: