If you for any reason have the need to merge / combine a few Nessus scans into a single *.nessus file, you can do so using this simple Python script. Since *.nessus files are basically just XML files with a different extension, what this script does is it finds all the *.nessus files in the current folder, finds all the “ReportHost” XML nodes accumulating them into a single report.nessus file which is then exported to nss_report folder.

Note that scans must be of the same type (same plugins must be used), but they can be from different subnets or different parts of the same subnet.

How to use it? – Put the script and all your *.nessus files into a same folder, run the script, import nss_report/report.nessus into Nessus – and there you have it, all the hosts are in one place..

If you have any questions, just drop a comment bellow..

Let’s say you need to filter a Python list and remove all elements that match a given criteria. If you wanted to remove a single element, you could just use ‘del list[i]‘ (example). But if you wanted to remove multiple elements this might be a problem since you would be modifying and iterating over the list at the same time (keeping track of list indexes can become very confusing, very fast).

A simple solution to this problem would be to keep record of all list elements (indexes) that need to be removed, and to remove tham afterwards. Also, one other thing to be wary about is that the removal process should be done in reverse because otherwise you would shift all the elements to the ‘left’ every time you removed an element from a list and you would (again) have to keep track of list indexes.

A simple function example:

This might not be the fastest ‘algorithm’ to do the job, but it works well enough for me..

Turning on History plugin in Pidgin will insert the last conversation into your current conversation. All this lastsaid entries can be found somewhere inside of blist.xml file which is located in your Pidgin conf directory (/home/username/.purple directory in GNU/Linux (not sure about where it is in MS Windows though)).

This is convinient if you want to view what was written before you accidentialy closed the chat window or if you forgot what were you last talking about with someone and if you want that information quickly. But, it is not convinient at all if you want to wipe it along with chat logs since lastsaid entries are at a different location and are not the only entries that can be found in blist.xml so you can’t just remove that file either. If you use a couple of protocols and have more than just a few buddies, removing lastsaid lines from blist.xml manually would probably prove to be pain in the ass.

So, what every curious programmer does in case he doesn’t have a feature he wants/needs? – He just makes it. :D Since I started playing with Python, I decided to create a small py3k script I could use every once in a while to completely wipe both lastsaid history and chat logs from Pidgin.

What you need to do to make this script work is – you need to put it into your Pidgin conf directory (just put it into a file called something.py) and after that just run the script (you need to have python installed on your machine to run this script).

I hope this helps. Also, if you have any questions/problems with the script, feel free to drop a comment..

(19:05:53) perovodokotlić: evo opet se dogodilo to
(19:05:57) perovodokotlić: ono kad ti padne nešto na pod ispod tebe
(19:05:58) perovodokotlić: i nestane
(19:06:04) perovodokotlić: trzalica
(19:06:06) perovodokotlić: nema je
(19:06:08) pootzko: :D
(19:06:10) perovodokotlić: pala mi je pod noge i nema je niiigdje
(19:06:12) pootzko: trzalice pogotovo
(19:06:16) pootzko: one kad padnu
(19:06:24) pootzko: otvore neki procjep u prostorno vremenskom kontinuumu
(19:06:31) pootzko: i odu u neki paralelni svemir
(19:06:34) pootzko: never to be found again
(19:06:39) perovodokotlić: hahaha
(19:07:59) pootzko: i šarafi isto
(19:08:00) pootzko: i neposlušne nikadprobavljene kokice

spontani red guglanja…

…i red slučajnog dalekointernetskog očitoistomišljenika

~ragetoons + ~mylifecomics

This one might just spare you about 2-3 hours of your time doing SVN+SSH kdesvn googling. One would think it would work out-of-the-box, but it doesn’t. To get kdesvn to work with SSH, there is one small undocumented trick – using an environment variable (as if you were using command line SVN+SSH). To do that, put the following line into your .bashrc:

If you try using SVN+SSH without it, kdesvn will try to login to remote server using your current username (the one you are using on your local machine). Of course, each time unsuccessfully because it’s not the right username. After that, go to Subversion->General->Checkout a repository, and enter:

…in the URL field. Also, choose the target directory and check any other desired options. After that, just bookmark the connection and you’re all set up.