Shoutbox

You woudn't need to really secure anything. MySQL databases itself are secure (providing you've setup the user accounts correctly) - among other things..

You can use an .htaccess method for web security along with Apache-SSL. - Among other things...

Getting the logs decryped from MSGPlus, I have no idea. Maybe Patchou can help you with that?

quote:

---

Originally posted by ipab
Patchou please provide me an alternative :*).

---

It would be cool if there was an api for it BUT it poped up with a messege saying "xxx is trying to decypt this log file allow?" followed by an input password dialog.

quote:

---

Originally posted by ipab
Seeing as it is encrypted in the harddrive it is wise to do the same online.

---

encrypted content would be every hard to search :/ i think...
* -dt- googles...

here is how I figure it can be done.

user prompted for pass (plugin prompt). The pass is verified with online md5 salt value in db. If correct then they are authorised to the search/delete functions of the logs. As for the logs itself, they are satled and hashed, only problem is that we are going to have to figure out a way to not show the salting method in the php file itself. Perhaps  the plugin adds a bunch of selected chars (we choose) and then salts it, therefore it is constant always. Only downfall to that is that they would have to use the plugin to check their logs (otherwise they have no other way of decrypting the hashes).

* -dt- just votes for it to be stored with a user configurable "Salt"
or make work easier for dt and store as plain text

searching encoded content would be hard , if you go that way we will have to download all the logs (or just a certain time period if the user chooses) from the mysql db then unencode them then run some crazy word finding thing /return the logs...

plain text is easy..... store it then use mysql's built in search function (though i do wish for this to be easy to port to other database's like sqlite...)


so ehhhhhhhhhhhhhhhhhhhhhhh maybe the best thing would be to ask the user how we store it? and impliment both

sounds good. Problem is I feel that we are getting ahead of ourselves here . I cant seem to figure out a mass port for the logs into the db.

quote:

---

Originally posted by ipab
sounds good. Problem is I feel that we are getting ahead of ourselves here . I cant seem to figure out a mass port for the logs into the db.

---

hmm..
* -dt- opens Vim and tries to parse them with preg_match....


edit: done it

code:

---

$x = file_get_contents('./chatlog.txt');


//this regexp matches the body of the text (the part where you talk )
$match = "/\.-{68}\.(?:.+)\.-{68}(.+)-{68}\./smUx";


//this regexp matches the header (part with dates n stuff)
$head = "/\.-{68}\.(.+)\.-{68}/smUx";

preg_match_all($match,$x,$data);
preg_match_all($head,$x,$header);

//show the first header
echo $header[1][0];

//show the first body
echo $data[1][0];

---

btw those regexp's are no where near pefect

i'm sorry to kick this message, but i hope Patchou will read it...

if patchou is able to allow us to create a second event log, with the following data: email, time/date, message and message-code*, I will volunteer to write a web-based script that allows you to read out the event log to statistics. (just not-encrypted files...)...

*a message code stands for the action taken, e.g. 1001 is OFFLINE, 1002 is CHANGE NAME .... never mind what codes, just to distinguish the messages