packages/warden-server-2.0.0-beta.tar.gz.sig

-01bfc44ba12f04f1a56386e4efca8e626f1cdbd1  warden-server-2.0.0-beta.tar.gz

packages/warden-server-2.0.tar.gz.sig

-9ad83d6d136358179d68c49255af0f426b564edc  warden-server-2.0.tar.gz

src/meta/README

-* customize wrapper's clown computing nodes selector
-** set SERVER, IP, BASE (2x) variables in scripts
-** http://meta.cesnet.cz/wiki/Pl%C3%A1novac%C3%AD_syst%C3%A9m_-_detailn%C3%AD_popis
-* connect to any job submitter frontend (arda, skirit, ...)
-** submit a job `qsub wtw-lenny-meta.sh`
-** monitor it `qstat -u $USER`
-
-* populate clients table
-** set USER, PASS, DB (other/importMetaClients.sh)
-** 'meta-nodes' must be in the same directory
-** run;)

src/meta/other/importMetaClients.sh

-#!/bin/bash
-
-USER=""
-PASS=""
-DB="warden"
-
-if [ -z $PASS ]; then
-	MYSQL_CMD="mysql -u$USER $DB";
-else
-	MYSQL_CMD="mysql -u$USER -p$PASS $DB";
-fi
-
-for host in `cat meta-nodes`; do
-	IP=`host $host | grep -v 'handle' | awk '{print $4}'`
-	echo "INSERT INTO clients VALUES (NULL, '$host', now(),'automatic', 'test', 's', NULL, 'n', 'bruteforce', '$IP/32');" | $MYSQL_CMD
-done 

src/meta/other/meta-nodes

-tarkil10-1.cesnet.cz
-tarkil10-2.cesnet.cz
-tarkil11-1.cesnet.cz
-tarkil11-2.cesnet.cz
-tarkil12-1.cesnet.cz
-tarkil12-2.cesnet.cz
-tarkil13-1.cesnet.cz
-tarkil13-2.cesnet.cz
-tarkil14-1.cesnet.cz
-tarkil14-2.cesnet.cz
-tarkil15-1.cesnet.cz
-tarkil15-2.cesnet.cz
-tarkil17-1.cesnet.cz
-tarkil17-2.cesnet.cz
-tarkil18-1.cesnet.cz
-tarkil18-2.cesnet.cz
-tarkil19-1.cesnet.cz
-tarkil19-2.cesnet.cz
-tarkil20-1.cesnet.cz
-tarkil20-2.cesnet.cz
-tarkil21-1.cesnet.cz
-tarkil21-2.cesnet.cz
-tarkil22-1.cesnet.cz
-tarkil22-2.cesnet.cz
-tarkil23-1.cesnet.cz
-tarkil23-2.cesnet.cz
-tarkil24-1.cesnet.cz
-tarkil24-2.cesnet.cz
-tarkil25-1.cesnet.cz
-tarkil25-2.cesnet.cz
-tarkil26-1.cesnet.cz
-tarkil26-2.cesnet.cz
-tarkil27-1.cesnet.cz
-tarkil27-2.cesnet.cz
-tarkil5-1.cesnet.cz
-tarkil5-2.cesnet.cz
-tarkil7-1.cesnet.cz
-tarkil7-2.cesnet.cz
-tarkil9-1.cesnet.cz
-tarkil9-2.cesnet.cz
-konos20-1.fav.zcu.cz
-perian55-1.ncbr.muni.cz
-skirit51-1.ics.muni.cz
-skirit51-2.ics.muni.cz
-skirit52-1.ics.muni.cz
-skirit52-2.ics.muni.cz
-skirit53-1.ics.muni.cz
-skirit53-2.ics.muni.cz
-skirit54-1.ics.muni.cz
-skirit54-2.ics.muni.cz
-skirit55-1.ics.muni.cz
-skirit55-2.ics.muni.cz
-skirit56-1.ics.muni.cz
-skirit56-2.ics.muni.cz
-skirit57-1.ics.muni.cz
-skirit57-2.ics.muni.cz
-skirit58-1.ics.muni.cz
-skirit58-2.ics.muni.cz
-skirit59-1.ics.muni.cz
-skirit59-2.ics.muni.cz
-skirit60-1.ics.muni.cz
-skirit60-2.ics.muni.cz
-skirit61-1.ics.muni.cz
-skirit61-2.ics.muni.cz
-skirit62-1.ics.muni.cz
-skirit62-2.ics.muni.cz
-skirit63-1.ics.muni.cz
-skirit63-2.ics.muni.cz
-skirit64-1.ics.muni.cz
-skirit64-2.ics.muni.cz
-skirit65-1.ics.muni.cz
-skirit65-2.ics.muni.cz
-skirit67-1.ics.muni.cz
-skirit67-2.ics.muni.cz
-skirit68-1.ics.muni.cz
-skirit68-2.ics.muni.cz
-skirit69-1.ics.muni.cz
-skirit69-2.ics.muni.cz
-skirit70-1.ics.muni.cz
-skirit70-2.ics.muni.cz
-skirit71-1.ics.muni.cz
-skirit71-2.ics.muni.cz
-skirit72-1.ics.muni.cz
-skirit72-2.ics.muni.cz
-skirit73-1.ics.muni.cz
-skirit73-2.ics.muni.cz
-skirit74-1.ics.muni.cz
-skirit74-2.ics.muni.cz
-skirit75-1.ics.muni.cz
-skirit75-2.ics.muni.cz
-skirit76-1.ics.muni.cz
-skirit76-2.ics.muni.cz
-skirit77-1.ics.muni.cz
-skirit77-2.ics.muni.cz
-skirit78-1.ics.muni.cz
-skirit78-2.ics.muni.cz
-skirit79-1.ics.muni.cz
-skirit79-2.ics.muni.cz
-skirit84-1.ics.muni.cz
-skirit84-2.ics.muni.cz
-perian10-1.ncbr.muni.cz
-perian10-2.ncbr.muni.cz
-perian11-1.ncbr.muni.cz
-perian11-2.ncbr.muni.cz
-perian1-1.ncbr.muni.cz
-perian12-1.ncbr.muni.cz
-perian12-2.ncbr.muni.cz
-perian1-2.ncbr.muni.cz
-perian13-1.ncbr.muni.cz
-perian13-2.ncbr.muni.cz
-perian14-1.ncbr.muni.cz
-perian14-2.ncbr.muni.cz
-perian15-1.ncbr.muni.cz
-perian15-2.ncbr.muni.cz
-perian16-1.ncbr.muni.cz
-perian16-2.ncbr.muni.cz
-perian17-1.ncbr.muni.cz
-perian17-2.ncbr.muni.cz
-perian18-1.ncbr.muni.cz
-perian18-2.ncbr.muni.cz
-perian19-1.ncbr.muni.cz
-perian19-2.ncbr.muni.cz
-perian20-1.ncbr.muni.cz
-perian20-2.ncbr.muni.cz
-perian21-1.ncbr.muni.cz
-perian21-2.ncbr.muni.cz
-perian2-1.ncbr.muni.cz
-perian22-1.ncbr.muni.cz
-perian22-2.ncbr.muni.cz
-perian2-2.ncbr.muni.cz
-perian23-1.ncbr.muni.cz
-perian23-2.ncbr.muni.cz
-perian24-1.ncbr.muni.cz
-perian24-2.ncbr.muni.cz
-perian25-1.ncbr.muni.cz
-perian25-2.ncbr.muni.cz
-perian26-1.ncbr.muni.cz
-perian26-2.ncbr.muni.cz
-perian27-1.ncbr.muni.cz
-perian27-2.ncbr.muni.cz
-perian28-1.ncbr.muni.cz
-perian28-2.ncbr.muni.cz
-perian29-1.ncbr.muni.cz
-perian29-2.ncbr.muni.cz
-perian30-1.ncbr.muni.cz
-perian30-2.ncbr.muni.cz
-perian31-1.ncbr.muni.cz
-perian31-2.ncbr.muni.cz
-perian3-1.ncbr.muni.cz
-perian32-1.ncbr.muni.cz
-perian32-2.ncbr.muni.cz
-perian3-2.ncbr.muni.cz
-perian33-1.ncbr.muni.cz
-perian33-2.ncbr.muni.cz
-perian34-1.ncbr.muni.cz
-perian34-2.ncbr.muni.cz
-perian35-1.ncbr.muni.cz
-perian35-2.ncbr.muni.cz
-perian36-1.ncbr.muni.cz
-perian36-2.ncbr.muni.cz
-perian37-1.ncbr.muni.cz
-perian37-2.ncbr.muni.cz
-perian38-1.ncbr.muni.cz
-perian38-2.ncbr.muni.cz
-perian39-1.ncbr.muni.cz
-perian39-2.ncbr.muni.cz
-perian40-1.ncbr.muni.cz
-perian40-2.ncbr.muni.cz
-perian4-1.ncbr.muni.cz
-perian4-2.ncbr.muni.cz
-perian5-1.ncbr.muni.cz
-perian5-2.ncbr.muni.cz
-perian6-1.ncbr.muni.cz
-perian6-2.ncbr.muni.cz
-perian7-1.ncbr.muni.cz
-perian7-2.ncbr.muni.cz
-perian8-1.ncbr.muni.cz
-perian8-2.ncbr.muni.cz
-perian9-1.ncbr.muni.cz
-perian9-2.ncbr.muni.cz
-loslab1-1.ics.muni.cz
-loslab1-2.ics.muni.cz
-loslab2-1.ics.muni.cz
-loslab2-2.ics.muni.cz
-loslab3-1.ics.muni.cz
-loslab3-2.ics.muni.cz
-loslab4-1.ics.muni.cz
-loslab4-2.ics.muni.cz
-loslab5-1.ics.muni.cz
-loslab5-2.ics.muni.cz
-loslab6-1.ics.muni.cz
-loslab6-2.ics.muni.cz
-manwe3.ics.muni.cz
-manwe4.ics.muni.cz
-loslab1.ics.muni.cz
-loslab2.ics.muni.cz
-loslab3.ics.muni.cz
-loslab4.ics.muni.cz
-loslab5.ics.muni.cz
-loslab6.ics.muni.cz
-perian55-2.ncbr.muni.cz
-skirit50.ics.muni.cz
-skirit51.ics.muni.cz
-skirit52.ics.muni.cz
-skirit53.ics.muni.cz
-skirit54.ics.muni.cz
-skirit55.ics.muni.cz
-skirit56.ics.muni.cz
-skirit57.ics.muni.cz
-skirit58.ics.muni.cz
-skirit59.ics.muni.cz
-skirit60.ics.muni.cz
-skirit61.ics.muni.cz
-skirit62.ics.muni.cz
-skirit63.ics.muni.cz
-skirit64.ics.muni.cz
-skirit65.ics.muni.cz
-skirit66.ics.muni.cz
-skirit67.ics.muni.cz
-skirit68.ics.muni.cz
-skirit69.ics.muni.cz
-skirit70.ics.muni.cz
-skirit71.ics.muni.cz
-skirit72.ics.muni.cz
-skirit73.ics.muni.cz
-skirit74.ics.muni.cz
-skirit75.ics.muni.cz
-skirit76.ics.muni.cz
-skirit77.ics.muni.cz
-skirit78.ics.muni.cz
-skirit79.ics.muni.cz
-skirit80.ics.muni.cz
-skirit84.ics.muni.cz
-perian10.ncbr.muni.cz
-perian11.ncbr.muni.cz
-perian12.ncbr.muni.cz
-perian13.ncbr.muni.cz
-perian14.ncbr.muni.cz
-perian15.ncbr.muni.cz
-perian16.ncbr.muni.cz
-perian17.ncbr.muni.cz
-perian18.ncbr.muni.cz
-perian19.ncbr.muni.cz
-perian1.ncbr.muni.cz
-perian20.ncbr.muni.cz
-perian21.ncbr.muni.cz
-perian22.ncbr.muni.cz
-perian23.ncbr.muni.cz
-perian24.ncbr.muni.cz
-perian25.ncbr.muni.cz
-perian26.ncbr.muni.cz
-perian27.ncbr.muni.cz
-perian28.ncbr.muni.cz
-perian29.ncbr.muni.cz
-perian2.ncbr.muni.cz
-perian30.ncbr.muni.cz
-perian31.ncbr.muni.cz
-perian32.ncbr.muni.cz
-perian33.ncbr.muni.cz
-perian34.ncbr.muni.cz
-perian35.ncbr.muni.cz
-perian36.ncbr.muni.cz
-perian37.ncbr.muni.cz
-perian38.ncbr.muni.cz
-perian39.ncbr.muni.cz
-perian3.ncbr.muni.cz
-perian40.ncbr.muni.cz
-perian4.ncbr.muni.cz
-perian5.ncbr.muni.cz
-perian6.ncbr.muni.cz
-perian7.ncbr.muni.cz
-perian8.ncbr.muni.cz
-perian9.ncbr.muni.cz
-tarkil10.cesnet.cz
-tarkil11.cesnet.cz
-tarkil12.cesnet.cz
-tarkil13.cesnet.cz
-tarkil14.cesnet.cz
-tarkil15.cesnet.cz
-tarkil17.cesnet.cz
-tarkil18.cesnet.cz
-tarkil19.cesnet.cz
-tarkil20.cesnet.cz
-tarkil21.cesnet.cz
-tarkil22.cesnet.cz
-tarkil23.cesnet.cz
-tarkil24.cesnet.cz
-tarkil25.cesnet.cz
-tarkil26.cesnet.cz
-tarkil27.cesnet.cz
-tarkil5.cesnet.cz
-tarkil7.cesnet.cz
-tarkil9.cesnet.cz
-konos10.fav.zcu.cz
-konos1.fav.zcu.cz
-konos2.fav.zcu.cz
-konos3.fav.zcu.cz
-konos4.fav.zcu.cz
-konos5.fav.zcu.cz
-konos6.fav.zcu.cz
-konos7.fav.zcu.cz
-konos8.fav.zcu.cz
-konos9.fav.zcu.cz
-tarkil8-1.cesnet.cz
-tarkil8-2.cesnet.cz
-tarkil8.cesnet.cz
-alela1-1.feec.vutbr.cz
-alela1-2.feec.vutbr.cz
-alela1.feec.vutbr.cz
-alela10-1.feec.vutbr.cz
-alela10-2.feec.vutbr.cz
-alela10.feec.vutbr.cz
-alela11-1.feec.vutbr.cz
-alela11-2.feec.vutbr.cz
-alela11.feec.vutbr.cz
-alela12-1.feec.vutbr.cz
-alela12-2.feec.vutbr.cz
-alela12.feec.vutbr.cz
-alela2-1.feec.vutbr.cz
-alela2-2.feec.vutbr.cz
-alela2.feec.vutbr.cz
-alela3-1.feec.vutbr.cz
-alela3-2.feec.vutbr.cz
-alela3.feec.vutbr.cz
-alela4-1.feec.vutbr.cz
-alela4-2.feec.vutbr.cz
-alela4.feec.vutbr.cz
-alela5-1.feec.vutbr.cz
-alela5-2.feec.vutbr.cz
-alela5.feec.vutbr.cz
-alela6-1.feec.vutbr.cz
-alela6-2.feec.vutbr.cz
-alela6.feec.vutbr.cz
-alela7-1.feec.vutbr.cz
-alela7-2.feec.vutbr.cz
-alela7.feec.vutbr.cz
-alela8-1.feec.vutbr.cz
-alela8-2.feec.vutbr.cz
-alela8.feec.vutbr.cz
-alela9-1.feec.vutbr.cz
-alela9-2.feec.vutbr.cz
-alela9.feec.vutbr.cz
-konos15-1.fav.zcu.cz
-konos15-2.fav.zcu.cz
-konos15.fav.zcu.cz
-konos17-1.fav.zcu.cz
-konos17-2.fav.zcu.cz
-konos17.fav.zcu.cz
-konos18-1.fav.zcu.cz
-konos18-2.fav.zcu.cz
-konos18.fav.zcu.cz
-konos20-2.fav.zcu.cz
-konos20.fav.zcu.cz
-konos22-1.fav.zcu.cz
-konos22-2.fav.zcu.cz
-konos22.fav.zcu.cz
-konos27-1.fav.zcu.cz
-konos27-2.fav.zcu.cz
-konos27.fav.zcu.cz
-konos30-1.fav.zcu.cz
-konos30-2.fav.zcu.cz
-konos30.fav.zcu.cz
-konos34-1.fav.zcu.cz
-konos34-2.fav.zcu.cz
-konos34.fav.zcu.cz
-hermes05-1.prf.jcu.cz
-hermes05-2.prf.jcu.cz
-hermes05.prf.jcu.cz
-orca1-1.ics.muni.cz
-orca1-2.ics.muni.cz
-orca1.ics.muni.cz
-orca10-1.ics.muni.cz
-orca10-2.ics.muni.cz
-orca10.ics.muni.cz
-orca11-1.ics.muni.cz
-orca11-2.ics.muni.cz
-orca11.ics.muni.cz
-orca12-1.ics.muni.cz
-orca12-2.ics.muni.cz
-orca12.ics.muni.cz
-orca13-1.ics.muni.cz
-orca13-2.ics.muni.cz
-orca13.ics.muni.cz
-orca14-1.ics.muni.cz
-orca14-2.ics.muni.cz
-orca14.ics.muni.cz
-orca15-1.ics.muni.cz
-orca15-2.ics.muni.cz
-orca15.ics.muni.cz
-orca16-1.ics.muni.cz
-orca16-2.ics.muni.cz
-orca16.ics.muni.cz
-orca17-1.ics.muni.cz
-orca17-2.ics.muni.cz
-orca17.ics.muni.cz
-orca18-1.ics.muni.cz
-orca18-2.ics.muni.cz
-orca18.ics.muni.cz
-orca2-1.ics.muni.cz
-orca2-2.ics.muni.cz
-orca2.ics.muni.cz
-orca3-1.ics.muni.cz
-orca3-2.ics.muni.cz
-orca3.ics.muni.cz
-orca5-1.ics.muni.cz
-orca5-2.ics.muni.cz
-orca5.ics.muni.cz
-orca6-1.ics.muni.cz
-orca6-2.ics.muni.cz
-orca6.ics.muni.cz
-orca7-1.ics.muni.cz
-orca7-2.ics.muni.cz
-orca7.ics.muni.cz
-orca8-1.ics.muni.cz
-orca8-2.ics.muni.cz
-orca8.ics.muni.cz
-orca9-1.ics.muni.cz
-orca9-2.ics.muni.cz
-orca9.ics.muni.cz
-quark11-1.video.muni.cz
-quark11-2.video.muni.cz
-quark11.video.muni.cz
-quark12-1.video.muni.cz
-quark12-2.video.muni.cz
-quark12.video.muni.cz
-quark13-1.video.muni.cz
-quark13-2.video.muni.cz
-quark13.video.muni.cz
-quark14-1.video.muni.cz
-quark14-2.video.muni.cz
-quark14.video.muni.cz
-quark15-1.video.muni.cz
-quark15-2.video.muni.cz
-quark15.video.muni.cz
-quark6-1.video.muni.cz
-quark6-2.video.muni.cz
-quark6.video.muni.cz
-quark7-1.video.muni.cz
-quark7-2.video.muni.cz
-quark7.video.muni.cz
-hermes07-1.prf.jcu.cz
-hermes07-2.prf.jcu.cz
-hermes07.prf.jcu.cz
-hermes08-1.prf.jcu.cz
-hermes08-2.prf.jcu.cz
-hermes08.prf.jcu.cz
-hermes09-1.prf.jcu.cz
-hermes09-2.prf.jcu.cz
-hermes09.prf.jcu.cz
-hermes10-1.prf.jcu.cz
-hermes10-2.prf.jcu.cz
-hermes10.prf.jcu.cz
-hermes03-1.prf.jcu.cz
-hermes03-2.prf.jcu.cz
-hermes03.prf.jcu.cz
-konos37-1.fav.zcu.cz
-konos37-2.fav.zcu.cz
-konos37.fav.zcu.cz
-tarkil1-1.cesnet.cz
-tarkil1-2.cesnet.cz
-tarkil1.cesnet.cz
-nympha1-1.zcu.cz
-nympha1-2.zcu.cz
-nympha1.zcu.cz
-nympha2-1.zcu.cz
-nympha2-2.zcu.cz
-nympha2.zcu.cz
-nympha3-1.zcu.cz
-nympha3-2.zcu.cz
-nympha3.zcu.cz
-nympha4-1.zcu.cz
-nympha4-2.zcu.cz
-nympha4.zcu.cz
-nympha5-1.zcu.cz
-nympha5-2.zcu.cz
-nympha5.zcu.cz
-nympha6-1.zcu.cz
-nympha6-2.zcu.cz
-nympha6.zcu.cz
-nympha7-1.zcu.cz
-nympha7-2.zcu.cz
-nympha7.zcu.cz
-nympha8-1.zcu.cz
-nympha8-2.zcu.cz
-nympha8.zcu.cz
-nympha9-1.zcu.cz
-nympha9-2.zcu.cz
-nympha9.zcu.cz
-hermes06-1.prf.jcu.cz
-hermes06-2.prf.jcu.cz
-hermes06.prf.jcu.cz
-quark9-1.video.muni.cz
-quark9-2.video.muni.cz
-quark9.video.muni.cz
-konos16-1.fav.zcu.cz
-konos16-2.fav.zcu.cz
-konos16.fav.zcu.cz
-konos24-1.fav.zcu.cz
-konos24-2.fav.zcu.cz
-konos24.fav.zcu.cz
-konos26-1.fav.zcu.cz
-konos26-2.fav.zcu.cz
-konos26.fav.zcu.cz
-konos36-1.fav.zcu.cz
-konos36-2.fav.zcu.cz
-konos36.fav.zcu.cz
-nympha10-1.zcu.cz
-nympha10-2.zcu.cz
-nympha10.zcu.cz
-tarkil16-1.cesnet.cz
-tarkil16-2.cesnet.cz
-tarkil16.cesnet.cz
-tarkil2-1.cesnet.cz
-tarkil2-2.cesnet.cz
-tarkil2.cesnet.cz
-ajax.zcu.cz
-eru1.ruk.cuni.cz
-eru2.ruk.cuni.cz
-hermes02-1.prf.jcu.cz
-hermes02-2.prf.jcu.cz
-hermes02.prf.jcu.cz
-nympha12-1.zcu.cz
-nympha12-2.zcu.cz
-nympha12.zcu.cz
-nympha13-1.zcu.cz
-nympha13-2.zcu.cz
-nympha13.zcu.cz
-nympha15-1.zcu.cz
-nympha15-2.zcu.cz
-nympha15.zcu.cz
-nympha16-1.zcu.cz
-nympha16-2.zcu.cz
-nympha16.zcu.cz
-nympha17-1.zcu.cz
-nympha17-2.zcu.cz
-nympha17.zcu.cz
-nympha19-1.zcu.cz
-nympha19-2.zcu.cz
-nympha19.zcu.cz
-quark10-1.video.muni.cz
-quark10-2.video.muni.cz
-quark10.video.muni.cz
-quark8-1.video.muni.cz
-quark8-2.video.muni.cz
-quark8.video.muni.cz
-hermes11-1.prf.jcu.cz
-hermes11-2.prf.jcu.cz
-hermes11.prf.jcu.cz
-orca4-1.ics.muni.cz
-orca4-2.ics.muni.cz
-orca4.ics.muni.cz
-hermes01-1.prf.jcu.cz
-hermes01-2.prf.jcu.cz
-hermes01.prf.jcu.cz
-quark16-1.video.muni.cz
-quark16-2.video.muni.cz
-quark16.video.muni.cz
-nympha11-1.zcu.cz
-nympha11-2.zcu.cz
-nympha11.zcu.cz
-nympha18-1.zcu.cz
-nympha18-2.zcu.cz
-nympha18.zcu.cz
-tarkil3-1.cesnet.cz
-tarkil3-2.cesnet.cz
-tarkil3.cesnet.cz
-tarkil28-1.cesnet.cz
-tarkil28-2.cesnet.cz
-tarkil28.cesnet.cz
-manwe1.ics.muni.cz
-manwe2.ics.muni.cz
-manwe5.ics.muni.cz
-manwe6.ics.muni.cz
-manwe7.ics.muni.cz
-perian55.ncbr.muni.cz
-skirit80-1.ics.muni.cz
-tarkil4-1.cesnet.cz
-tarkil4-2.cesnet.cz
-tarkil4.cesnet.cz
-tarkil6-1.cesnet.cz
-tarkil6-2.cesnet.cz
-tarkil6.cesnet.cz
-nympha14-1.zcu.cz
-nympha14-2.zcu.cz
-nympha14.zcu.cz
-skirit83.ics.muni.cz
-skirit83-1.ics.muni.cz
-skirit83-2.ics.muni.cz
-luna3.fzu.cz
-apollo1.fzu.cz
-apollo2.fzu.cz
-apollo3.fzu.cz
-perian56-1.ncbr.muni.cz
-perian56-2.ncbr.muni.cz
-perian56.ncbr.muni.cz
-perian41-1.ncbr.muni.cz
-perian41-2.ncbr.muni.cz
-perian41.ncbr.muni.cz
-perian42-1.ncbr.muni.cz
-perian42-2.ncbr.muni.cz
-perian42.ncbr.muni.cz
-perian43-1.ncbr.muni.cz
-perian43-2.ncbr.muni.cz
-perian43.ncbr.muni.cz
-perian44-1.ncbr.muni.cz
-perian44-2.ncbr.muni.cz
-perian44.ncbr.muni.cz
-perian45-1.ncbr.muni.cz
-perian45-2.ncbr.muni.cz
-perian45.ncbr.muni.cz
-perian46-1.ncbr.muni.cz
-perian46-2.ncbr.muni.cz
-perian46.ncbr.muni.cz
-perian47-1.ncbr.muni.cz
-perian47-2.ncbr.muni.cz
-perian47.ncbr.muni.cz
-perian48-1.ncbr.muni.cz
-perian48-2.ncbr.muni.cz
-perian48.ncbr.muni.cz
-perian49-1.ncbr.muni.cz
-perian49-2.ncbr.muni.cz
-perian49.ncbr.muni.cz
-perian50-1.ncbr.muni.cz
-perian50-2.ncbr.muni.cz
-perian50.ncbr.muni.cz
-perian51-1.ncbr.muni.cz
-perian51-2.ncbr.muni.cz
-perian51.ncbr.muni.cz
-perian52-1.ncbr.muni.cz
-perian52-2.ncbr.muni.cz
-perian52.ncbr.muni.cz
-perian53-1.ncbr.muni.cz
-perian53-2.ncbr.muni.cz
-perian53.ncbr.muni.cz
-perian54-1.ncbr.muni.cz
-perian54-2.ncbr.muni.cz
-perian54.ncbr.muni.cz
-skirit80-2.ics.muni.cz
-minos1.zcu.cz
-minos1-1.zcu.cz
-minos1-2.zcu.cz
-minos2.zcu.cz
-minos2-1.zcu.cz
-minos2-2.zcu.cz
-minos3.zcu.cz
-minos3-1.zcu.cz
-minos3-2.zcu.cz
-minos4.zcu.cz
-minos4-1.zcu.cz
-minos4-2.zcu.cz
-minos5.zcu.cz
-minos5-1.zcu.cz
-minos5-2.zcu.cz
-minos6.zcu.cz
-minos6-1.zcu.cz
-minos6-2.zcu.cz
-minos7.zcu.cz
-minos7-1.zcu.cz
-minos7-2.zcu.cz
-minos8.zcu.cz
-minos8-1.zcu.cz
-minos8-2.zcu.cz
-minos9.zcu.cz
-minos9-1.zcu.cz
-minos9-2.zcu.cz
-minos10.zcu.cz
-minos10-1.zcu.cz
-minos10-2.zcu.cz
-minos11.zcu.cz
-minos11-1.zcu.cz
-minos11-2.zcu.cz
-minos12.zcu.cz
-minos12-1.zcu.cz
-minos12-2.zcu.cz
-minos13.zcu.cz
-minos13-1.zcu.cz
-minos13-2.zcu.cz
-minos14.zcu.cz
-minos14-1.zcu.cz
-minos14-2.zcu.cz
-minos15.zcu.cz
-minos15-1.zcu.cz
-minos15-2.zcu.cz
-minos16.zcu.cz
-minos16-1.zcu.cz
-minos16-2.zcu.cz
-minos17.zcu.cz
-minos17-1.zcu.cz
-minos17-2.zcu.cz
-minos18.zcu.cz
-minos18-1.zcu.cz
-minos18-2.zcu.cz
-minos19.zcu.cz
-minos19-1.zcu.cz
-minos19-2.zcu.cz
-minos20.zcu.cz
-minos20-1.zcu.cz
-minos20-2.zcu.cz
-minos21.zcu.cz
-minos21-1.zcu.cz
-minos21-2.zcu.cz
-minos22.zcu.cz
-minos22-1.zcu.cz
-minos22-2.zcu.cz
-minos23.zcu.cz
-minos23-1.zcu.cz
-minos23-2.zcu.cz
-minos24.zcu.cz
-minos24-1.zcu.cz
-minos24-2.zcu.cz
-minos25.zcu.cz
-minos25-1.zcu.cz
-minos25-2.zcu.cz
-minos26.zcu.cz
-minos26-1.zcu.cz
-minos26-2.zcu.cz
-minos27.zcu.cz
-minos27-1.zcu.cz
-minos27-2.zcu.cz
-minos28.zcu.cz
-minos28-1.zcu.cz
-minos28-2.zcu.cz
-minos29.zcu.cz
-minos29-1.zcu.cz
-minos29-2.zcu.cz
-minos30.zcu.cz
-minos30-1.zcu.cz
-minos30-2.zcu.cz
-minos31.zcu.cz
-minos31-1.zcu.cz
-minos31-2.zcu.cz
-minos32.zcu.cz
-minos32-1.zcu.cz
-minos32-2.zcu.cz
-minos33.zcu.cz
-minos33-1.zcu.cz
-minos33-2.zcu.cz
-minos34.zcu.cz
-minos34-1.zcu.cz
-minos34-2.zcu.cz
-minos35.zcu.cz
-minos35-1.zcu.cz
-minos35-2.zcu.cz
-minos36.zcu.cz
-minos36-1.zcu.cz
-minos36-2.zcu.cz
-minos37.zcu.cz
-minos37-1.zcu.cz
-minos37-2.zcu.cz
-minos38.zcu.cz
-minos38-1.zcu.cz
-minos38-2.zcu.cz
-minos39.zcu.cz
-minos39-1.zcu.cz
-minos39-2.zcu.cz
-minos40.zcu.cz
-minos40-1.zcu.cz
-minos40-2.zcu.cz
-minos41.zcu.cz
-minos41-1.zcu.cz
-minos41-2.zcu.cz
-minos42.zcu.cz
-minos42-1.zcu.cz
-minos42-2.zcu.cz
-minos43.zcu.cz
-minos43-1.zcu.cz
-minos43-2.zcu.cz
-minos44.zcu.cz
-minos44-1.zcu.cz
-minos44-2.zcu.cz
-minos45.zcu.cz
-minos45-1.zcu.cz
-minos45-2.zcu.cz
-minos46.zcu.cz
-minos46-1.zcu.cz
-minos46-2.zcu.cz
-minos47.zcu.cz
-minos47-1.zcu.cz
-minos47-2.zcu.cz
-minos48.zcu.cz
-minos48-1.zcu.cz
-minos48-2.zcu.cz
-minos49.zcu.cz
-minos49-1.zcu.cz
-minos49-2.zcu.cz
-skirit66-1.ics.muni.cz
-skirit66-2.ics.muni.cz
-luna1.fzu.cz
-mandos1.ics.muni.cz
-mandos2.ics.muni.cz
-mandos3.ics.muni.cz
-mandos4.ics.muni.cz
-mandos5.ics.muni.cz
-mandos6.ics.muni.cz
-mandos7.ics.muni.cz
-mandos8.ics.muni.cz
-mandos9.ics.muni.cz
-mandos10.ics.muni.cz
-mandos11.ics.muni.cz
-mandos12.ics.muni.cz
-mandos13.ics.muni.cz
-mandos14.ics.muni.cz

src/meta/other/meta_check.sh

-#!/bin/bash
-#Logovatko poctu prenesenych zprav na Warden server a vytizeni serveru
-
-
-USER=root
-PASS=
-DB=warden
-INT=1
-
-QUERY="SELECT NOW(), COUNT( id ), COUNT(DISTINCT(note)) FROM events WHERE received > DATE_SUB(UTC_TIMESTAMP(), INTERVAL $INT MINUTE) AND service='test';"
-
-M_OUT=`echo $QUERY | mysql -s -u$USER -p"$PASS" $DB`
-U_OUT=`uptime | awk '{print $11}'`
-RET="${M_OUT} ${U_OUT%?}"
-echo $RET

src/meta/wardentest-lenny-meta.sh

-#!/bin/bash
-
-#IP serveru 
-SERVER=""
-PORT=""
-
-#Cesta ke scriptum a zdrojakum, typicky AFS, napr. /afs/zcu.cz/users/v/vomacka/public/wardentest
-BASE=""
-
-HNAME=`hostname -f`
-
-# STAGEIN
-WDIR="/scratch/${PBS_O_LOGNAME}/wardentest.$$"
-mkdir -p $WDIR || exit 1
-cd $WDIR
-
-tar xzf $BASE/warden-client-meta.tgz 
-perl -pi -e "s#\[path\]#$WDIR#" performance-sender.pm
-perl -pi -e "s#\[path\]#$WDIR#" etc/warden-client.conf
-perl -pi -e "s#\[server\]#$SERVER#" etc/warden-client.conf
-perl -pi -e "s#\[port\]#$PORT#" etc/warden-client.conf
-
-openssl req -new -nodes -keyform PEM -outform PEM -config ./ca/openssl.cnf -keyout ./ca/server-key.pem -out ./ca/server.csr -subj "/CN=$HNAME" -days 365 
-openssl ca -batch -keyform PEM -passin pass:test -name client_ca -config ./ca/openssl.cnf -out ./ca/server-cert.pem -infiles ./ca/server.csr
-
-# JOB
-for i in `seq 1 1000`; do 
-./performance-sender.pm test 10 &> /dev/null
-done
-
-date
-
-# STAGEOUT
-#cp p1.log $BASE/output-p1.log.$PBS_JOBID.$HNAME
-#cp p2.log $BASE/output-p2.log.$PBS_JOBID.$HNAME
-cd /tmp
-rm -rf $WDIR
-

src/meta/wtw-lenny-meta.sh

-#!/bin/bash
-#PBS -N wtw-lenny.sh
-#PBS -q short
-#PBS -l nodes=1:ppn=1:^cl_luna
-#PBS -j oe
-#PBS -m abe
-#
-# describtion from 'man qsub':
-# -N ... declares a name for the job.  The name specified may be up to and including 15 characters in  length.   It
-#        must consist of printable, non white space characters with the first character alphabetic.
-# -q ... defines the destination of the job (queue)
-# -l ... defines  the  resources that are required by the job
-# -j oe ... standard error stream of the job will be merged with the standard output stream
-# -m ace ...  mail is sent anytime
-
-#in file name of which can be found in variable PBS_NODEFILE, is list of allocated machines
-echo '***PBS_NODEFILE***START*******'
-cat $PBS_NODEFILE
-echo '***PBS_NODEFILE***END*********'
-
-#Cesta ke scriptum a zdrojakum, typicky AFS, napr. /afs/zcu.cz/users/v/vomacka/public/wardentest
-BASE=""
-cd $BASE || exit 1
-
-# spusti dany prikaz na vsech pridelenych strojich
-pbsdsh -o -- bash ${BASE}/wardentest-lenny-meta.sh
-
-

src/warden-client/bin/receiver.pl

-#!/usr/bin/perl -w
-#
-# receiver.pl
-#
-# Copyright (C) 2011-2012 Cesnet z.s.p.o
-#
-# Use of this source is governed by a BSD-style license, see LICENSE file.
-
-use strict;
-
-my $warden_path = '/opt/warden-client';
-require $warden_path . '/lib/WardenClientReceive.pm';
-
-#my $requested_type = "copyright";
-#my $requested_type = "botnet_c_c";
-my $requested_type = "bruteforce";
-my @new_events = WardenClientReceive::getNewEvents($warden_path, $requested_type);
-
-print "+------------------------------------------------------------------------------------------------------------------------------------------+\n";
-print "| id | hostname | service | detected | type | source_type | source | target_proto | target_port | attack_scale | note | priority | timeout |\n";
-print "+------------------------------------------------------------------------------------------------------------------------------------------+\n";
-
-foreach (@new_events) {
-  print "| " . join(' | ', @$_) . " |" . "\n";
-}
-print "+------------------------------------------------------------------------------------------------------------------------------------------+";
-print "\n";
-print "Last events in: " . scalar(localtime(time)) . "\n";
-
-exit 0;

src/warden-client/bin/sender.pl

-#!/usr/bin/perl -w
-#
-# sender.pl
-#
-# Copyright (C) 2011-2012 Cesnet z.s.p.o
-#
-# Use of this source is governed by a BSD-style license, see LICENSE file.
-
-use Switch;
-use strict;
-use DateTime;
-
-my $warden_path = '/opt/warden-client';
-require $warden_path . '/lib/WardenClientSend.pm';
-
-my $service = "";
-switch (int(rand(2) + 0.5)) {
-  case 0 { $service = 'ScanDetector'; }
-  case 1 { $service = 'PhiGaro'; }
-  case 2 { $service = 'HoneyScan'; }
-  }
-
-my $detected = DateTime->from_epoch(epoch => time());
-
-my $type = "";
-switch (int(rand(9) + 0.5)) {
-  case 0 { $type = 'portscan'; }
-  case 1 { $type = 'bruteforce'; }
-  case 2 { $type = 'spam'; }
-  case 3 { $type = 'phishing'; }
-  case 4 { $type = 'botnet_c_c'; }
-  case 5 { $type = 'dos'; }
-  case 6 { $type = 'malware'; }
-  case 7 { $type = 'copyright'; }
-  case 8 { $type = 'webattack'; }
-  case 9 { $type = 'other'; }
-  }
-  
-my $source_type = "";
-switch (int(rand(2) + 0.5)) {
-  case 0 { $source_type = 'IP'; }
-  case 1 { $source_type = 'url'; }
-  case 2 { $source_type = 'Reply-To:'; }
-  }
-
-my $source = (int(rand(254) + 0.5) + 1) . "." . (int(rand(254) + 0.5) + 1) . "." . (int(rand(254) + 0.5) + 1) . "." . (int(rand(254) + 0.5) + 1);
-
-my $target_proto = "";
-switch (int(rand(1) + 0.5)) {
-  case 0 { $target_proto = 'TCP'; }
-  case 1 { $target_proto = 'UDP'; }
-  }
-
-my $target_port = "";
-switch (int(rand(5) + 0.5)) {
-  case 0 { $target_port = '22'; }
-  case 1 { $target_port = '23'; }
-  case 2 { $target_port = '25'; }
-  case 3 { $target_port = '443'; }
-  case 4 { $target_port = '3389'; }
-  case 5 { $target_port = 'null'; }
-  }
-
-my $attack_scale = (int(rand(100000) + 0.5) + 1000);
-
-my $note = "tohle je takova normalni jednoducha poznamka";
-
-my $priority = "";
-switch (int(rand(1) + 0.5)) {
-  case 0 { $priority = int(rand(255) + 0.5); }
-  case 1 { $priority = 'null'; }
-  }
-  
-my $timeout = "";
-switch (int(rand(1) + 0.5)) {
-  case 0 { $timeout = int(rand(255) + 0.5); }
-  case 1 { $timeout = 'null'; }
-  } 
-
-my @event = (
-  $service, # $service
-  "$detected", # $detected
-  $type, # $type
-  $source_type, # $source_type
-  $source, # $source
-  $target_proto, # $target_proto
-  $target_port, # $target_port
-  $attack_scale, # $attack_scale
-  $note, # $note
-  $priority, # $priority
-  $timeout, # $timeout
-  );
-
-WardenClientSend::saveNewEvent($warden_path, \@event);
-
-#foreach (@event) {
-#  print "$_\n";
-#}

src/warden-client/doc/AUTHORS

-AUTHORS AND MAINTAINERS :
-
-MAIN DEVELOPERS:
-Tomas Plesnik   	<plesnik@ics.muni.cz>
-Jan Soukal      	<soukal@ics.muni.cz>
-Michal Kostenec 	<kostenec@civ.zcu.cz>
-
-CONTRIBUTORS:
-Vit Slama		<slama@cis.vutbr.cz>
-Martin Drasar		<drasar@ics.muni.cz>
-
-TESTING:
-Jakub Cegan		<cegan@ics.muni.cz>
-
-DEVELOPMENT MANAGER:
-Jan Vykopal		<vykopal@ics.muni.cz>
-
-PROJECT MANAGERS:
-Pavel Kacha		<ph@cesnet.cz>
-Andrea Kropacova	<andrea@cesnet.cz>
-
-COMMUNITY:
-Radoslav Bodo		<bodik@civ.zcu.cz>
-Radomir Orkac		<orkac@cesnet.cz>

src/warden-client/doc/CHANGELOG

-2012-00-00 v.2.1 stable version
--------------------------------
-- receiving of all types of messages now supported
-- added support for batch processing
-- maximum number of events received ($MAX_RCV_EVENTS_LIMIT) in one batch can 
-  be set in etc/warden-client.conf. Default is 6000.
-
-
-2012-07-27 v.2.0 stable version and bugfix release of warden-client-2.0.0-beta
-------------------------------------------------------------------------------
-- Sender client code fixed, so that it will not terminate "parent"
-  application when crashed
-
-
-2012-05-10 v.2.0.0-beta beta version of warden-client-2.0.0
------------------------------------------------------------
-- Changed communication with server: HTTP layer added (compatible with
-  Apache mod_perl version of Warden server)
-- Removed Linux version check in install.sh, unistall.sh and update.sh
-- Removed shell (BASH) dependencies in install.sh, unistall.sh and update.sh
-    
-
-2012-03-30 v1.2.0 stable version and bugfix release of warden-client-1.1.0
---------------------------------------------------------------------------
-- Fixed SSL certificate/key access privileges security issue
-- Fixed client crash after multiple events download
-- Fixed install.sh crash when warden client installation dictionary doesn't exist
-- Fixed configuration error in permission access to etc directory in update.sh
-- Fixed bug in backup process in update.sh
-- Fixed several small bugs/issues
-
-
-2012-02-06 v1.1.0 stable version and bugfix release of warden-client-1.0.0
---------------------------------------------------------------------------
-- Fixed bug when receiving of events
-- Fixed earlier declaration in same scope of variable $data
-- Fixed errMsg function -> finishing by the die function
-- Added client configuration module WardenClientConf.pm
-- Added error message when warden server is down
-- Added README.cesnet (CESNET Specifics) file
-- Added uninstallation script -> uninstall.sh
-- Added update script -> update.sh
-- Fixed several small bugs/issues
-
-
-2011-11-16 v1.0.0 stable version
---------------------------------
-- Initial package of warden client
-- SSL certificate authentication/authorization supported
-- Automatized installation process

src/warden-client/doc/INSTALL

-Installation process
---------------------
-
-For installation of warden-client package on local machine use install.sh.
-  
-Default destination directory is /opt/warden-client/.
-          
-For more information about install.sh options run install.sh -h.
-
-You must be root for running this script.
-
-
-Uninstallation process
-----------------------
-
-For uninstallation of warden-client package from local machine use uninstall.sh.
-  
-Default uninstallation directory is /opt/warden-client/.
-          
-For more information about uninstall.sh options run uninstall.sh -h.
-
-You must be root for running this script.

src/warden-client/doc/README

-+----------------------------+
-| README - Warden Client 2.0 |
-+----------------------------+
-
-Content
-
- A. Overall Information
- B. Installation Dependencies
- C. Installation
- D. Update
- E. Uninstallation
- F. Configuration
- G. Registration
- H. Integration with Local Applications
- I. Functions, Arguments and Calls
-
-
---------------------------------------------------------------------------------
-A. Overall Information
-
- 1. About Warden Client
- 
-    Warden is a client-based architecture service designed to share detected
-    security events (issues) among CSIRT and CERT teams in a simple and fast
-    way.
-    
-    This package offers a client capable of both reporting events to server and 
-    retreiving batch of new events from server. It consists of several Perl 
-    modules/libraries which should be included into detection applications.
- 
- 2. Version
-  
-    2.0 (2012-07-27)
-    
- 3. Package structure
- 
-    warden-client/
-      doc/
-        CHANGELOG
-        example-sender.pl.txt
-        example-receiver.pl.txt
-	      INSTALL
-	      LICENSE
-	      README
-	      README.cesnet
-      etc/
-        warden-client.conf
-	      package_version
-      lib/
-        WardenClientConf.pm
-        WardenClientSend.pm
-        WardenClientReceive.pm  
-      var/
-
-
---------------------------------------------------------------------------------
-B. Installation Dependencies
-  
-    Perl                  >= 5.10.1  
-    SOAP::Lite            >= 0.712
-    IO::Socket::SSL       >= 1.74
-    SOAP::Transport::HTTP >= 0.712
-    FindBin               >= 1.50
-    DateTime              >= 0.61
-
-
---------------------------------------------------------------------------------
-C. Installation (First installation of the Warden client package)
-
- 1. Check SHA1 checksum of corresponding Warden client package archive
-
-    $ sha1sum -c warden-client-2.0.tar.gz.sig
-
- 2. Untar it
-
-    $ tar xzvf warden-client-2.0.tar.gz
-
- 3. Run install.sh 
-  
-    Default destination directory is /opt/warden-client/
-    
-    For more information about install.sh options run install.sh -h
-
-    You must be root for running this script.
-
- 4. Installation Privileges
-
-    The Warden client is designed to be run under standard privileges. It should 
-    be a part of other applications that are run under usual user privileges.
-    However, the Warden client uses SSL certificates for security purposes which
-    are often not accessible by standard users.
-
-    To solve this issue, the Warden client should be installed under root
-    privileges. It copyies local SSL key and certificate files into 
-    warden-client/etc folder where those are accessible even with standard 
-    privileges.
-
-    Should users want to preserve standard location of certificate files,
-    they are advised to remove key and certificate files after installation
-    from warden-client/etc/ and manually edit paths to certificate files in
-    warden-client/etc/warden-client.conf. In most cases, this change will force
-    the Warden client to be run under root privileges though.
-
- 5. Configuration file
-
-    After successful installation process you are advised to check configuration
-    file warden-client/etc/warden-client.conf. For more information see section
-    below F. Configuration.
-
- 6. Usage of install.sh
-
-    Usage: install.sh [-d <directory>] [-u <user>] [-k <ssl_key_file>]
-                      [-c <ssl_cert_file>] [-a <ssl_ca_file>] [-hV]
-	-d <directory>            installation directory (default: /opt)
-	-u <user>                 owner of warden client package (user for
-				                    running detection scripts)
-	-k <ssl_key_file>         SSL certificate key file path
-	-c <ssl_cert_file>        SSL certificate file path
-	-a <ssl_ca_file>          CA certificate file path
-	-h                        print this help
-	-V                        print script version number and exit
-	
-    Example: # ./install.sh -d /opt -u detector -k /etc/ssl/private/client.key
-    			    -c /etc/ssl/certs/client.pem -a /etc/ssl/certs"
-
-
---------------------------------------------------------------------------------
-D. Update (Update of previously installed the Warden client package)
-
- 1. Check SHA1 checksum of corresponding the Warden client package archive
-
-    $ sha1sum -c warden-client-2.0.tar.gz.sig
-
- 2. Untar it
-
-    $ tar xzvf warden-client-2.0.tar.gz
-
- 3. Run update.sh 
-  
-    Default destination directory is /opt/warden-client/
-    
-    For more information about update.sh options run update.sh -h
-
-    You must be root for running this script.
-
- 4. Configuration file
-
-    After successful update process you are advised to check configuration
-    file warden-client/etc/warden-client.conf. For more information see section
-    F. Configuration.
-
- 5. Usage of update.sh
-
-    Usage: update.sh [-d <directory>] [-hV]
-        -d <directory>            destination directory (default: /opt)
-        -h                        print this help
-        -V                        print script version number and exit
-
-    Example: # ./update.sh -d /opt
-
-    Note: You must be root for running this script.
-
-
---------------------------------------------------------------------------------
-E. Uninstallation
-
- 1. Run uninstall.sh 
-  
-    The script is located in warden-client package directory. 
-    
-    Default uninstallation directory is /opt/warden-client/.
-    
-    For more information about uninstall.sh options, run uninstall.sh -h.
-
-    You must be root for running this script.
-
- 2. Usage of uninstall.sh
-
-    Usage: uninstall.sh [-d <directory>] [-hV]
-        -d <directory>            uninstallation directory (default: /opt)
-        -h                        print this help
-        -V                        print script version number and exit
-
-    Example: # ./uninstall.sh -d /opt
-
-    Note: You must be root for running this script.
-
-
---------------------------------------------------------------------------------
-F. Configuration
-    
-    SOAP protocol is used for handling communication between server and clients.
-    Therefore, correct URI of the Warden server must be set.
-
-    Authentication of clients and server is performed using client and server
-    SSL certificates. Both clients and server must have valid certificate.
-
-    Configuration file contains following parameters:
-
-    URI 	  - URI of the Warden server
-          	    e.g. 'https://mywarden.server.com:443/Warden'
-
-    SSL_KEY_FILE  - path to a host key file,
-    	    	    e.g. '/opt/warden-client/etc/mywarden.server.com.key'
-
-    SSL_CERT_FILE - path to a host certificate file,
-     		    e.g. '/opt/warden-client/etc/mywarden.server.com.pem'
-
-    SSL_CA_FILE   - path to a CA file
-                    e.g. '/etc/ssl/certs/tcs-ca-bundle.pem' 
-
-
-    Client receives events in batches. Maximum number of events received in one
-    batch can is set in MAX_RCV_EVENTS_LIMIT. Note that this option only
-    affects clients that receives events from the Warden server (e.g., uses
-    lib/WardenClientReceive.pm module).
-
-    MAX_RCV_EVENTS_LIMIT - maximum number of events in one batch    
-                         - default set to 6000, which generates app. 250 MB
-                           of memory consumption.
-                         - only affects "receiving" clients
-
-
---------------------------------------------------------------------------------
-G. Registration
-
-    Any client attempting to communicate with the Warden server must be
-    registered on this server. Unknown (not registered) clients are not allowed
-    to exchange any data with server.
-  
-    Registration of your client is provided by the Warden server administrator.
-    Usually via e-mail.
-  
-    Clients also need to have valid client SSL certificates to prove their
-    identity to the Warden server. 
-  
-    Each client is defined by its hostname, service name, type of client, type
-    of requested events, receiving of own events, description tags and CIDR
-    this client is allowed to communicate from.
-  
-    Hostname  hostname of client to be registered
-
-    Service name              Text string. Unique name of the service the client
-                              is integrated in.
-                              E.g. 'ScanDetector_1.0'. This is mandatory for
-                              'Sender' client. Default value null is used for
-                              'Receiver' client.
-
-    Type of client            Either 'Sender' or 'Receiver'.
-
-    Type of requested events  Type of events the client only accepts from
-                              the Warden server. This is mandatory only for
-                              'Receiver' client. Default value null is used
-                              for 'Sender' client. Brief information about
-                              event types is provided in section I. Functions
-                              arguments and calls.
-
-    Receiving of own events   Enables receiving of events sent from your
-                              organization domain = yes/no (organizations are
-                              separated based on the top-level and
-                              second-level domain). This is mandatory only
-                              for 'Receiver' client.
-
-    Description tags          Tags are case insensitive alphanumeric strings
-                              designed to allow event receivers to filter
-                              according to event source. For example, 
-                              receiver can decide to use only events 
-                              originating from honeypots or filter out events
-                              generated manually by users. This is mandatory
-                              for 'Sender' client.
-
-    CIDR                      CIDR stands for IP (sub)net the client is going
-                              to communicate from (see examples below!). Any
-                              communications between the client and the Warden
-                              server must be performed from IP address from
-                              a range stated in CIDR.
-                              Examples: '123.123.0.0/16', '123.123.123.123/32'
-
-  
-    For complete information about client attributes and/or event types you will
-    have to contact particular Warden server administrator/provider.
-
-
---------------------------------------------------------------------------------       
-H. Integration with Local Applications
- 
- (Note: Clients need to be registered on server to be able to communicate with
-        server properly. See section G. Registration for more information about
-        client registration.)
- 
- 1. Client sender (this type of client reports events to the Warden server)
-  
-    Client is included as a Perl module (WardenClientSend.pm) into Perl code of 
-    local detection application.   
-   
-    See warden-client/doc/example-sender.pl.txt for example how to use
-    the Warden client sender.
-    
-    Brief information about syntax of sending functions and functionality is
-    provided in section I. Functions, Arguments and Calls.
- 
- 2. Client receiver (this type of clients downloads events from the Warden 
-    server)
- 
-    Client is included as a Perl module (WardenClientReceive.pm)
-    into Perl code of local 'reaction' application or may be used as core of
-    standalone local application.
-      
-    See warden-client/doc/example-receiver.pl.txt for example how to use
-    the Warden client receiver.   
-    
-    Brief information about syntax of receiving functions is provided in 
-    section I. Functions, Arguments and Calls. 
-
-
---------------------------------------------------------------------------------
-I. Functions, Arguments and Calls
-
- 1. WardenClientSend::saveNewEvent
- 
-    A function to report one event to the Warden server. See example 'Sender'
-    client in warden-client/doc/example-sender.pl.txt
-    
-    Function call (Perl):
-    
-    # Path to warden-client folder
-    $warden_path = '/opt/warden-client';
-    
-    # Inclusion of the Warden client sender module
-    require $warden_path . '/lib/WardenClientSend.pm';
-    
-    # Sending event to the Warden server
-    WardenClientSend::saveNewEvent($warden_path, \@event);
-    
-    Event array is defined as (Perl):
-    
-    @event = ($service, $detected, $type, $source_type, $source, $target_proto,
-              $target_port, $attack_scale, $note, $priority, $timeout );
-
-    Event array attributes with example value and explanation on the right
-    (Perl):
-
-    # SERVICE - VARCHAR (64)
-    # Name of a service detecting this event. Service must be the same with this
-    # provided in 'Sender' client registration. See more about this issue in
-    # section G. Registration.    
-    $service      = "ScanDetector";
-
-    # DETECTED - TIMESTAMP in UTC, ISO 8601
-    # Date and time when was event detected.
-    $detected     = "2011-07-16T19:20:30.45";
-    
-    # TYPE - VARCHAR (64)
-    # Type of reported event. Currently supported values are:
-    # darkspace   - access into honeypot segment
-    # portscan    - scannig of TCP/UDP ports
-    # bruteforce  - bruteforce/dictionary attack against authentication
-    #               service(s)
-    # probe       - other connection attempts (for example ICMP) or
-    #               unrecognized/undecided portscan or bruteforce
-    # spam        - unsolicited e-mail that does not have phishing-like
-    #               character
-    # phishing    - e-mail attempting to gather sensitive data
-    # botnet_c_c  - command and control center of botnet
-    # dos         - (distributed) denial of service attack
-    # malware     - virus sample
-    # copyright   - copyright infringement issue
-    # webattack   - attack against web application
-    # other       - anything that does not match any of previous categories
-    $type         = "portscan";
-    
-    # SOURCE_TYPE - VARCHAR 64
-    # Type of source of reported attack/issue. Currently supported values are:
-    # IP, URL, Reply-To:, null
-    $source_type  = "IP";
-    
-    # SOURCE - VARCHAR 256
-    # identification of an attack source/origin according to source_type
-    $source       = "123.123.123.123";
-    
-    # TARGET_PROTO - VARCHAR 16
-    # Protocol type of reported attack/issue target. Supported are all L3 and L4
-    # protocols and null. 
-    $target_proto = "TCP";
-    
-    # TARGET_PORT - INT 2
-    # Port number of reported attack/issue target or null.
-    $target_port  = "22";
-    
-    # ATTACK_SCALE - INT 4
-    # Definition of attack scale, e.g., number of affected targets. Null is also
-    # possible when attack scale is not known or clear enough.
-    $attack_scale = "1234567890";
-    
-    # NOTE - TEXT
-    # Some important(!) note or comment or null. Also, it may contain virus
-    # sample, phishing e-mail with headers and other accordingly to event type.
-    $note         = "this threat is dangerous";
-    
-    # PRIORITY - INT 1
-    # Subjective definition of incident severity. Values 0-255 or null are
-    # possible where 0 is the lowest priority.
-    $priority     = "null";
-    
-    # TIMEOUT - INT 2
-    # Subjective time (in minutes) or null. After this time event might be
-    # considered timeouted.
-    $timeout      = "20";
-
-    The return value of function SaveNewEvent is 1 when an event was
-    successfully received by the Warden server. Otherwise, the return value
-    is 0.
-
- 2.  WardenClientReceive::getNewEvents
-
-    A function to download batch of events from the Warden server. Received
-    events are stored in @events array. See example 'Receiver' client in
-    warden-client/doc/example-receiver.pl.txt
-    
-    Function call (perl):
-    
-    # Path to warden-client directory
-    my $warden_path = '/opt/warden-client';
-
-    # Inclusion of warden-client receiving functionality
-    require $warden_path . '/lib/WardenClientReceive.pm';
-
-    # Definition of requested event type. Type must be the same with this
-    # provided in 'Receiver' client registration. See more about this issue in
-    # section G. Registration. See more about event types in section
-    # I. 1. WardenClientSend::saveNewEvent
-    $requested_type = "botnet_c_c";
-
-    # Download batch of new events from the Warden server
-    @new_events = WardenClientReceive::getNewEvents($warden_path,
-                                                    $requested_type);
-                                                    
-    Structure of each received event in the event array equals to those 
-    explained in section I. 1. WardenClientSend::saveNewEvent. It has one 
-    additional attribute ID - unique id of this particular event (BIGINT).
-
---------------------------------------------------------------------------------
-
-Copyright (C) 2011-2012 Cesnet z.s.p.o
-

src/warden-client/doc/README.cesnet

-+-----------------------------------+
-| README.cesnet - Warden Client 2.0 |
-|				    |
-| CESNET Specifics                  |
-+-----------------------------------+
-
-Content
-
- A. Overall Information
- B. Registration
- C. Description tags
- D. Types of events
- E. Configuration
- F. Testing
- G. Authors of this document
-
---------------------------------------------------------------------------------
-A. Overall Information
-
- 1. About CESNET Warden Server
-
-    Warden is a client-based architecture service designed to share detected
-    security events (issues) among CSIRT and CERT teams in a simple and fast way.
-
-    CESNET offers Warden server for security events exchange within its networks.
-
- 2. Version
-
-    2.0 (2012-07-27)
-
---------------------------------------------------------------------------------
-B. Registration
-
-    Client attempting to communicate with CESNET Warden server must be
-    registered. Registration is currently provided by Tomas Plesnik at
-    mail address plesnik@ics.muni.cz and following information is needed:
-
-    * For sender client:
-      - hostname of the machine, where client runs,
-      - client type = sender,
-      - name of the detection service (for example 'ScanDetector'),
-      - description tags of sent events (see below)
-      - CIDR from which client will communicate with Warden server.
-
-    * For receiver client:
-      - hostname of the machine, where client runs,
-      - client type = receiver,
-      - whether client should receive all events, or type of requested
-        events (for example 'portscan', see below) otherwise
-      - receiving of sent events from my organization = yes/no (organizations
-        are separated based on the top-level and second-level domain),
-      - CIDR from which client will communicate with Warden server.
-
-    Clients need to have valid certificate to prove their identity to the
-    Warden server. For CESNET network, 'server' type certificate from Terena
-    Certificate Service (provided by Comodo) is needed. Hostname of the
-    machine must correspond with certificate subject, Alternative Name
-    extension is not supported. Administrator of Warden client must be
-    entitled to obtain this certificate. CESNET TCS request service 
-    interface resides at
-
-      https://tcs.cesnet.cz/
-
---------------------------------------------------------------------------------
-C. Description tags
-
-   Tags are case insensitive alphanumeric strings, designed to allow event
-   receivers to do more general filtering according to event source. Receiver
-   can for example decide to use only events originating at honeypots, or
-   filter out events, generated by human conclusions or correlation engines.
-
-   Sender client specifies its descriptive tags during registration, it is
-   up to client administrator's judgment to select or omit any particular tag.
-   Currently tags fall into four general categories - based on event medium,
-   data source, detection methodology and detector or analyzer product name.
-   Product name tag is free to choose if same product name was not yet
-   accepted by registrar, otherwise existing form must be used (registrar will
-   notify about such cases).
-   Categories list is certainly not complete. Therefore if new client's
-   administrator feels that name or type of important feature of his (or
-   others) detector is not covered, providers of Warden server are glad to
-   discuss it at registration address or at Warden project mailing list 
-   (warden@cesnet.cz).
-   However, it may or may not be accepted, as aim is to keep the list of
-   categories possibly unambiguous, short and usable.
-
-   Following is grouped list of tags together with closer description and
-   examples.
-
- 1. Detection medium
-
-    * Network - network data based (Snort, Suricata, Bro, FTAS, LaBrea, Kippo,
-                Dionaea)
-    * Host - host based (Swatch, Logcheck)
-    * Correlation - corellation engines (Prelude, OSSIM)
-    * External - credible external sources (incident reporting, ticket
-                 systems, human verified events)
-
- 2. Data source
-
-    * Content - datagram content based detectors (Snort, Bro)
-    * Flow - netflow based (FTAS, FlowMon, HoneyScan)
-    * Connection - connection data (portscan, portsweep)
-    * Data - application data based (SpamAssassin, antiviruses)
-    * Log - based on system logs, where more specific source is not
-            applicable (Swatch, Logcheck, SSH scans)
-    * IR - incident reporting, ticket systems, human verified events
-
- 3. Detection methodology
-
-    * Honeypot (LaBrea, Kippo, Dionaea)
-    * Antispam (SpamAssassin, Bogofilter, CRM114, Policyd, greylisting)
-    * Antivirus (ClamAV)
-    * IDS - IDS/IPS, Snort, Suricata, Bro
-
- 4. Detector/analyzer product name examples
-
-    * Snort, FTAS, SpamAssassin, LaBrea, Swatch, Prelude, Kippo, Dionaea
-
---------------------------------------------------------------------------------
-D. Types of events
-
-   Event types purpose is to allow event receivers to filter and/or categorise
-   particular events according to attack characteristics. Types are loosely
-   chosen as list of common security incidents nowadays observed. List is by no
-   means complete, however it was created based on expected use cases at
-   receiving places. Possibility of a new type is also open to discussion.
-
-   * portscan - TCP/UDP port scanning/sweeping
-   * bruteforce - dictionary/bruteforce attack to services authentication
-   * probe - other connection attempts (for example ICMP) or
-             unrecognized/undecided portscan or bruteforce
-   * spam - unsolicited commercial email (except phishing)
-   * phishing - email, trying to scam user to revealing personal information
-     (possibly by some other channel)
-   * botnet_c_c - botnet command & control master machine
-   * dos - (possibly distributed) denial of service attack
-   * malware - virus/malware sample
-   * copyright - copyright infringement
-   * webattack - web application attack
-   * test - clients can use these at will when debugging/testing, these
-            messages will be processed and stored, but ignored later
-   * other - the rest, uncategorizable yet
-
-   In case of complex scenarios with structured info more events with
-   particular parts of information can be created.
-
---------------------------------------------------------------------------------
-E. Configuration
-
-    CESNET Warden server resides at URI 'https://warden.cesnet.cz:443/Warden'.  
-
---------------------------------------------------------------------------------       
-F. Testing
-
-    For testing purposes of sender clients, event type 'test' can be used.
-    These events will end up in server database, but will not be taken
-    further into consideration.
-
---------------------------------------------------------------------------------
-G. Authors of this document
-
-    Pavel Kacha     <ph@cesnet.cz>
-    Jan Soukal      <soukal@ics.muni.cz>
-
-Copyright (C) 2011-2012 Cesnet z.s.p.o

src/warden-client/doc/example-receiver.pl.txt

-#!/usr/bin/perl -w
-#
-# Copyright (C) 2011-2012 Cesnet z.s.p.o
-#
-# Use of this source is governed by a BSD-style license, see LICENSE file.  
-
-use strict;
-
-#------------------------------------------------------------------------------
-# Warden 2.0 Client, Receiver, Example
-#
-# Simple use of warden-client receiver functionality to download new events
-# from # Warden server. This code illustrates how to integrate warden-client
-# receive functionality into local applications.
-#------------------------------------------------------------------------------
-
-#------------------------------------------------------------------------------
-# This code should developer add into his/her application.
-
-# Path to warden-client directory
-my $warden_path = '/home/soukal/client-test/2.0.0_beta/warden-client/';
-
-# Inclusion of warden-client receiving functionality
-require $warden_path . '/lib/WardenClientReceive.pm';
-
-# Definition of requested event type. This attributes is also set on server
-# and must not change.
-my $requested_type = "portscan";
-
-#------------------------------------------------------------------------------
-# Simple code that prints out new events obtained from Warden server.
-
-print "+------------------------------------------------------------------------------------------------------------------------------------------+\n";
-print "| id | hostname | service | detected | type | source_type | source | target_proto | target_port | attack_scale | note | priority | timeout |\n";
-print "+------------------------------------------------------------------------------------------------------------------------------------------+\n";
-
-# Download of new evetns from Warden server
-while (my @new_events = WardenClientReceive::getNewEvents($warden_path, $requested_type)) {
-  foreach my $event_ref (@new_events) {
-    my @event = @$event_ref;
-    print "| " . join(' | ', @event) . " |" . "\n";
-  }
-print "+------------------------------------------------------------------------------------------------------------------------------------------+\n";
-}
-
-print "+------------------------------------------------------------------------------------------------------------------------------------------+";
-print "\n";
-print "Last events in: " . scalar(localtime(time)) . "\n";
-
-exit 0;

src/warden-client/doc/example-sender.pl.txt

-#!/usr/bin/perl -w
-#
-# Copyright (C) 2011-2012 Cesnet z.s.p.o
-#
-# Use of this source is governed by a BSD-style license, see LICENSE file.  
-
-use strict;
-use DateTime;
-
-#-------------------------------------------------------------------------------
-# Warden 2.0. Client, Sender, Example 
-#
-# Sample script using warden-client sending functionality. This example is not
-# intended to be a standalone script. It only shows how to use warden-client
-# functionality.
-#-------------------------------------------------------------------------------
-
-#-------------------------------------------------------------------------------
-# Preparation of event attributes.
-# This should be handled by detection application.
-
-
-my $local_detected = DateTime->from_epoch(epoch => time());
-
-
-my $service 		= "ScanDetector";
-my $detected 		= "$local_detected";
-my $type 		= "portscan";
-my $source_type 	= "IP";
-my $source 		= "123.123.123.123";
-my $target_proto 	= "TCP";
-my $target_port 	= "22";
-my $attack_scale 	= "1234567890";
-my $note 		= "important note or comment";
-my $priority 		= "null";
-my $timeout 		= "20";
-
-my @event 		= ($service, $detected, $type, $source_type, $source,
-			   $target_proto, $target_port, $attack_scale, $note,
-			   $priority, $timeout );
-
-#-------------------------------------------------------------------------------
-# Use of warden-client sender.
-# This code should developer add to his/her detection application
-# (with corresponding paths appropriately changed).
-
-# Path to warden-client folder
-my $warden_path = '/opt/warden-client';
-
-# Inclusion of warden-client sender module
-require $warden_path . '/lib/WardenClientSend.pm';
-
-# Sending event to Warden server
-WardenClientSend::saveNewEvent($warden_path, \@event);
-
-exit 0;