There is a bug that affects the use mktwpol.cfg (if anybody besides me actually uses that). If UPDATETW is set in mktwpol.cfg, it will override the fact that twsetup intends to avoid the use of the limited set of tripwire setup functions provided by mktwpol.sh (encrypt policy file, create tripwaire database). Also, if QUIET is set in mktwpol.cfg, it will stifle the progress reporting as mktwpol.sh generates the plain-text policy.
mktwpol.cfg should and does have priority for how mktwpol.sh runes when mktwpol.sh is called form the command line. Some code has been added to mktwpol.sh that facilitates a MODE_TWSETUP. mktwpol.cfg still has priority in MODE_TWSETUP, except QUIET is always switched off, and mktwpol.sh's routines for encrypting the policy file and making the tripwire database can't be called.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a bug that affects the use mktwpol.cfg (if anybody besides me actually uses that). If UPDATETW is set in mktwpol.cfg, it will override the fact that twsetup intends to avoid the use of the limited set of tripwire setup functions provided by mktwpol.sh (encrypt policy file, create tripwaire database). Also, if QUIET is set in mktwpol.cfg, it will stifle the progress reporting as mktwpol.sh generates the plain-text policy.
mktwpol.cfg should and does have priority for how mktwpol.sh runes when mktwpol.sh is called form the command line. Some code has been added to mktwpol.sh that facilitates a MODE_TWSETUP. mktwpol.cfg still has priority in MODE_TWSETUP, except QUIET is always switched off, and mktwpol.sh's routines for encrypting the policy file and making the tripwire database can't be called.