| 42 | | == Build audit plugins == |
| | 42 | == Procedure to build audit plugins == |
| | 43 | |
| | 44 | This is a two-step procedure. First we need to call setup-autogen.py to generate setup.py files inside each audit directory. |
| | 45 | |
| | 46 | {{{ |
| | 47 | $ cd audits/ |
| | 48 | $ ./setup-autogen.py passive/ |
| | 49 | $ ./setup-autogen.py active/ |
| | 50 | }}} |
| | 51 | |
| | 52 | Then we need to actually build the audits (pack the source files inside ump UMIT Plugin file format). To do this just type: |
| | 53 | |
| | 54 | {{{ |
| | 55 | $ ./setup-autogen.py -b passive/ |
| | 56 | $ ./setup-autogen.py -b active/ |
| | 57 | }}} |
| | 58 | |
| | 59 | This will generate various ump files inside the `audits/compiled` directory. Now the last step to use the audits inside PacketManipulator is just to add that path in the plugins path (this is achieved by adding a new entry pointing to this directory by using the Plugin Window / Paths tab). |
| | 60 | |
| | 61 | === Building or updating just a single audit === |
| | 62 | |
| | 63 | Please note that `setup-autogen.py` script can be used also for updating/creating just one single audit. The syntax is the same: |
| | 64 | |
| | 65 | {{{ |
| | 66 | $ ./setup-autogen.py passive/fingerprint # This will create setup.py |
| | 67 | $ ./setup-autogen.py -b passive/fingerprint # This will actually build the ump file inside audits/compiled |
| | 68 | }}} |
