Here is what i would do:

1. remove all un-needed modules. Specially all modules that have possibility to add some content (like: fileupload modules, gallery etc)

2. Walk throuh your files+folders and do a proper chmod

3. Read all you logfiles (httpd, xoops) frequently

4. Search for Any exploit´s on your os/software/modules/system/etc and be a step before any intruders

5. Password checks (remove accounts with short passwords)

6. If you host the system: check your firewall rules/logs

7. If you host the system: Add a security module to apache - here is a nice one:http://www.modsecurity.org/

8. Add .htaccess files to prevent access to special folders.

9. If you host the system: Block IP-adresses in youre firewall

10. If you host the system: Remove un-needed services and only accept http-trafic to the system.

11. setup a honey-trap and collect evidence/logs


And remember....they will read this to...

One simple thing could be to use a .htaccess file to block ip-adresses from accessing your Xoops.

I have good experiences with that, when i blocked out the whole ip-series for Brasil and Uruguy (lots of script-kidds there !)

Ciao !

Hi there dude´s/dudett´s !

Does it exist any guideline/howto for converting "add on´s" from xxx Nuke (or Mambo) into
Xoops ?

I have done a little script in Python to convert modules from:
Xoops-->E-Xoops/RunCMS -->Ciamos

My goal is to extend this script to handle the xxx Nuke add on´s as
well.

PhpNuke
PostNuke ---> XOOPS --> RunCMS/E-Xoops --> Ciamos
xyzNuke ?
Mambo ?

I know that this must sound crazy, but the fact is that most
modules can be converted by this script today, and will work
allmost "out of the box". The only main problem issue today is the degree of smarty support in the module.

So....is there any module hackers out there with experience of converting modules from xyz Nuke/Mambo into XOOPS that could share their experiences ?

best regards.

the dude