Menu

mktwpol-0.1.5 and twsetup-0.0.4

Bugs
cboldt
2013-09-14
2013-09-17
  • cboldt

    cboldt - 2013-09-14

    I've found a few minor things, but so far nothing that alarms me. I've got a version 0.2.0 all but complete. Version bump because it includes the fairly radical change of separating the RULENAME[] and asscoiated assignment out of the script proper, and into a "mktwpol.rules" file. The (also new) Makefile will install the mktwpol.rules file into /etc/tripwire. I think that's the best place, as it is an admin configuration, not a file is suited to /usr/share any more than twpol.txt is.

    On the one hand, the slow pickup of mktwpol by users is "disappointing" (not really, I do this for a personal hobby, and don't expect an audience!); on the other hand, I'm glad not many people have been bothered with the bugs.

    If you are one of the few who is using this and has a wish, suggestion, bug report, etc., don't be bashful.

     
  • Anonymous

    Anonymous - 2013-09-17

    A couple of the changes happening between 0.1.5 and a to-be-released 0.2.0 ...

    • Fixed a bug where plain-text policy header always pointed to a tw.cfg, even if the user had defined a different tripwire config file
    • Fixed an error in post set-up tutorial for non-default location with non-default tw config, e.g., /etc/tw-sandbox/goofy.cfg

    Other changes aim to reduce the chance a user will make a mistake that wastes much time or effort, and to make fully correct statements about what the script is going to do (or did), and what commands the user might find useful after tripwire is installed and set-up.

    Edit to add: Hahahah. Posted as anonymous - didn't even know I wasn't logged on!

     

    Last edit: cboldt 2013-09-17

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB