Daniel Carrera spake unto us the following wisdom: > Against this particular attack, Monotone only has recovery. Monotone has > a great recovery system, but something in the way of prevention or > detection would be a worthy improvement. For example: > > 1) Prevention: Remove or somehow restrict the "db kill_rev_locally" > command and the "db execute" command. > > 2) Detection: Record who runs "db kill_rev_locally" (recording "db > execute" is kind of pointless).
Monotone *cannot* have anything but recovery. If the attacker has
write access to your database on the filesystem (which is necessary
for thsi attack), he/she can just fire up 'sqlite' and remove as many
records as desired. It doesn't matter what monotone wrote or
annotated, in that case.
In general, yes, audit trails are great -- but make sure your
prevention and detection match the threat model you're supposing.
Ethan
--
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764
signature.asc
Description: Digital signature
_______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
