Making PHPNuke more secure:A Way Forward

Posted: Mon Feb 23, 2004 9:27 am

I went back through the code... reloaded a archived mainfile.php and redid it...

It worked this time without the errors.. don't know what wnet wrong last time...

Posted: Mon Feb 23, 2004 10:56 am

steven111 wrote:

Caching is the next thing..... for example, function returning active modules does not change from on user to the next, and from one day to the next. This is not a good example, as the table is small, but on big tables and joins it start to make an impact.

What about caching IP or usergroup based ?

Cos there are users and users and both have different privileges on a website if a groups system is used.

A file where you can setup the caching would best i think.
For example

Code:

$blocks = array(
"blocktitle" => "cachetime",
"blocktitle" => "cachetime",
"blocktitle" => "cachetime"
);
$module = array(
"title" => "cachetime",
"title" => "cachetime",
"title" => "cachetime"
);

So you can setup how long a part has to be cached before it's cached again.
Then make differences in "anon" and "member"

then cachetime * anon = totaltime to cache block

For example

Code:

$membertime = 1;
$anonymtime = 10;
$blocks = array(
"Survey" => "60" // 60 seconds
);
if (is_user($user)) {
$cachetime = $blocks["Survey"] * $membertime;
} else {
$cachetime = $blocks["Survey"] * $anonymtime;
}

if (filetime + $cachetime < time()) {
cache again;
} else {
echo cache;
}

Lieutenant Joined: Dec 30, 2003 Posts: 283

Good one, dj. There are many areas in the code ripe for caching.

Also note that Raven and I have had extensive discussions on this, and there is code available as well, at http://www.ravenphpscripts.com/posts1033-highlightsteven.html%2A

steve