Core File Modifications Nukesentinel mainfile.php

New Member Joined: Jun 29, 2007 Posts: 12

Hi,

My mainfile.php (nuke 8.0) differs from examples given.

Firstly, the examples given says it is based on Patched 3.1 mainfile.php

What is a Patched 3.1 mainfile.php?

Is it essential to use a patched mainfile.php and if so where do I get one?

If not essential, how do I deal with the first difference where it says:-

#
#-----[ OPEN ]------------------------------------------
#
mainfile.php

#
#-----[ FIND ]------------------------------------------
#
if(defined('FORUM_ADMIN')) {
define('INCLUDE_PATH', '../../../');
} elseif(defined('INSIDE_MOD')) {
define('INCLUDE_PATH', '../../');
} else {
define('INCLUDE_PATH', './');
}

@require_once(INCLUDE_PATH."config.php");
@require_once(INCLUDE_PATH."db/db.php");

#
#-----[ AFTER ADD ]------------------------------------------
#
@require_once(INCLUDE_PATH."includes/nukesentinel.php");

....................So I find:

if(defined('FORUM_ADMIN')) {
define('INCLUDE_PATH', '../../../');
} elseif(defined('INSIDE_MOD')) {
define('INCLUDE_PATH', '../../');
} else {
define('INCLUDE_PATH', './');
}

// Include the required files
@require_once(INCLUDE_PATH."config.php");

if(!$dbname) {
die(" <center><img src=images/logo.gif> There seems that PHP-Nuke isn't installed yet. (The values in config.php file are the default ones) You can proceed with the <a href='./install/index.php'>web installation</a> now.</center>");
}

@require_once(INCLUDE_PATH."db/db.php");

So this bit:
if(!$dbname) {
die(" <center><img src=images/logo.gif> There seems that PHP-Nuke isn't installed yet. (The values in config.php file are the default ones) You can proceed with the <a href='./install/index.php'>web installation</a> now.</center>");
}
...............is not in the example.

Do Ijust add?
@require_once(INCLUDE_PATH."includes/nukesentinel.php");

after

@require_once(INCLUDE_PATH."db/db.php");

and ignore the bit not in the example?

Thanks
(there are further changes/differences in this file but hey, one-at-a-time!)

Posted: Mon Jul 09, 2007 1:08 pm

I think that will work.

You do know that if you grab the latest RavenNuke it already has Sentinel installed, right? Wink

Posted: Mon Jul 09, 2007 2:05 pm

Hi,
Thanks, I will investigate.

Posted: Mon Jul 09, 2007 2:40 pm

Hi,

Looks like RavenNuke for my next install, I do have 3 sites already running nuke 8.0 (one of which got hacked - so I rebuilt it - hence wanting sentinel now).

This current install is a practice run on a test-bed nuke 8.0 site, which I am practicing installing NukeSentinel on before I try to install it on my flagship site.,

The differences between the examples and my mainfile.php are significant, what should I do?

Thanks.

Posted: Mon Jul 09, 2007 3:06 pm

I have not looked at 8.0, but I did install Sentinel on a 7.9 site before abandoning PHP-Nuke for RavenNuke. There were many small differences in the core file edits in the Sentinel documentation and what I saw in 7.9, but most of them were easy to reconcile after studying the code. Of course this is easy only if you are somewhat familiar with PHP and programming in general. I asked a question or two here on these forums and got it resolved. You could try that route.

If you aren't comfortable with that, you could perhaps post in the For-Hire forum and have someone do the edits for you.

If you really are concerned about security you'll want to switch to RavenNuke. Not only does it already have Sentinel and the security patches integrated, it also has fixed lots of bugs and security holes. Maybe it would be better to start thinking about a transition path to RavenNuke. But that is your decision to make based on your own scenario, goals, resources, etc.

Posted: Mon Jul 09, 2007 3:20 pm

Hello Gremmie

Thanks for your thoughts - I will do both in that case, I need to continue with the nuke 8.0 sites already running and will try the for hire route. Also I will do a test install of RavenNuke on my test site.

Thanks again