|
|
|
|
|
|
by tinus_hn
3436 days ago
|
|
|
Okay, so the problem arises due to: * bad luck so a signedness issue doesn't cause a warning * the use of the worst possible value as the invalid value * no testing * no defense in depth: no other component in the system appears to notice a file with such a dangerous mode set |
|
|