Differences between revisions 1 and 2
Revision 1 as of 2005-05-14 16:24:48
Size: 331
Editor: anonymous
Comment:
Revision 2 as of 2005-05-14 16:45:41
Size: 705
Editor: anonymous
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
When finished with the Debian packaging scripts, modify twpol.txt & twcfg.txt to your liking. Make sure that paths to the database in each file are the same. Then run the following commands to re-encrypt them:{{{
    twadmin -m P twpol.txt
==First Time Setup

When finished with the Debian packaging scripts, modify twpol.txt & twcfg.txt to your liking. Make sure that paths to the database in each file are the same. Then run the following commands to re-compile them:{{{
    twadmin -m P -S site.key twpol.txt
Line 6: Line 8:
Both configuration files are converted into a binary format, then signed with the site key. The plain text configurations can now be removed to prevent humans from reading them. However these files are not encrypted, so anyone with the twadmin binary will be able to decode them.

Now initialize your first database:{{{
    tripwire -m i
}}}

==First Time Setup

When finished with the Debian packaging scripts, modify twpol.txt & twcfg.txt to your liking. Make sure that paths to the database in each file are the same. Then run the following commands to re-compile them:

    twadmin -m P -S site.key twpol.txt
    twadmin -m F -S site.key twcfg.txt

Both configuration files are converted into a binary format, then signed with the site key. The plain text configurations can now be removed to prevent humans from reading them. However these files are not encrypted, so anyone with the twadmin binary will be able to decode them.

Now initialize your first database:

    tripwire -m i