[FAQ] ReHIPS failsafe mechanisms and mitigations (part 1)

Started by fixer, February 01, 2019, 08:19:11 AM

Previous topic - Next topic


There are lots of failsafe mechanisms and mitigations implemented in ReHIPS. This series of blogposts covers some of them. It's not essential to know them all, but it's always comforting to know that ReHIPS is ready for non-standard situations. Just in case.

1. All database operations use transactions. It's always sad to loose data when something enexpected happens during file write operations. Don't worry, ReHIPS uses custom made transactions, so either all changes are made into database or no changes at all, database won't be corrupted in any case. And it doesn't matter, whether these are programs database operations or settings database.

2. ReHIPS uses minimal possible privileges and access rights. For each and every action ReHIPS takes it tries to use minimal possible privileges and access rights. For example, when any handle is opened, only minimal necessary access rights are requsted. Having a service, it's possible to have and enable a lot of privileges, but only necessary ones are included. This serves two purposes: the less rights you request, the less possible it's to fail due to some filtering and denied access; from security point of view it may not be safe to run swinging a full access handle, when you only need to query limited information.