From 47f97fb35b521d0be1a407d11e42813746b03bef Mon Sep 17 00:00:00 2001 From: Rob Date: Wed, 23 Sep 2009 09:35:48 +0200 Subject: [PATCH] Small change in HTML layout of signduterre --- signduterre.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/signduterre.py b/signduterre.py index f09a5ad..22059bc 100755 --- a/signduterre.py +++ b/signduterre.py @@ -170,9 +170,9 @@ Arguments enclosed in []-brackets will be hidden in the output. That is, '[/proc '[1]' in the output (or '[n]' with n the number of the hidden argument), equivalent to the use of the --quiet option. This means the hidden arguments must be entered again when using the --check-file (-c) option. -[[[/p]]][[[h2]]] +[[[/p]]][[[h1 align="CENTER"]]] Signature-du-Terroir -[[[/h2]]][[[p]]] +[[[/h1]]][[[p]]] A very simple tool to generate a signature that can be used to test the integrity of files and "states" in a running installation. signduterre.py constructs a signature of the current system state and checks installation state with a previously made signature. The files are hashed with a passphrase to allow detection @@ -267,9 +267,9 @@ At the bottom, a 'TOTAL HASH' line will be printed that hashes all the lines pri includes the file names as printed on the hash lines. It is not inconceivable that existing signature files could have been compromised in ways that might be missed when checking the signature. The total hash will point out such changes. -[[[/p]]][[[h2]]] +[[[/p]]][[[h3]]] SECURITY -[[[/h2]]][[[LONG]]][[[p]]] +[[[/h3]]][[[LONG]]][[[p]]] When run on a compromised system, signduterre.py can be subverted if the attacker keeps a copy of all the files and command outputs, and reroutes the open() and stat() functions, or simply delegating signduterre.py to a chroot jail with the original system. In principle, signduterre.py only checks whether the computer -- 2.11.4.GIT