forks/linsk
forks/linsk
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add missing "or" in serious bug disclosure "unless" field

Browse source
This commit is contained in:
AlexSSD7 2023-09-30 12:23:16 +01:00
commit 5da507e4fc
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -45,7 +45,7 @@ Linsk relies on network file shares to expose files to the host machine. Below a
# ⚠️ Serious bug disclosures (Obsolete versions)
Linsk versions below **v0.2.0** are considered obsolete **UNLESS**:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size; **or**
* The experimental USB passthrough was used.
More information: [serious-bug-disclosures/README.md](serious-bug-disclosures/README.md)

2
serious-bug-disclosures/README.md
View file

@ -3,7 +3,7 @@
## Obsolete versions (Summary)
Linsk versions below **v0.2.0** are considered obsolete **UNLESS**:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size; **or**
* The experimental USB passthrough was used.
## Index

2
serious-bug-disclosures/faulty-block-size-detection.md
View file

@ -4,7 +4,7 @@
* **Affected versions**: below v0.2.0.
* **Affected *UNLESS***:
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size.
* The use of Linsk was limited exclusively to devices with a 512-byte logical block (sector) size; **or**
* The experimental USB passthrough was used.
* **Possible outcomes**: A disk may be locked to Linsk after writing a considerable amount of data through Linsk. This means that the disk will not be accessible by any Linux machine, unless a 512-byte block size is emulated. Reformat is required to recover from this condition.
* **Severity**: Although there is **no data loss**, the severity can be considered as **High**.