|
|
|
|
|
by swhipple
3408 days ago
|
|
I don't quite understand the real world use-case Veriexec is designed to solve. 1) Prevent tampering by making part of the system immutable? The fingerprint isn't necessary; unconditionally prevent modification to the relevant files instead. 2) Prevent tampering by using trusted files? Normally this should be done by having a set of trusted keys, not hardcoded hashes. That way you can still securely upgrade the system. 3) Accessing files from a remote untrusted filesystem? This doesn't seem to work either; see the caveats section in veriexec(9). Am I missing something here? |
|