Jump to content

Installer still present


Guest Michael

Recommended Posts

Doesn't really matter to me at all, I have enough sense to delete the directory :)



Same here, but some people do not. I always delete the install and upgrade directories after each install/upgrade. :)

I was just suggesting it as I felt IPS should implement that in as an added security feature.
Link to comment
Share on other sites

I would go one step further and prohibit use of the board entirely until the install.php file is removed from the installation directory. If people do not understand that an important part of the installation is to remove the installer before going "click to log in" then they really shouldn't be doing the install IMO.

Link to comment
Share on other sites

That may sound good in theory, but if people try to connect to your board and cant access it, its 1 of 2 things. You have turned it off, or you forgot your installer, and then in that case they may just go and reinstall your forum.

I like the idea of moving it to the security panel, and when there is a security update it loads that page first. +1

Link to comment
Share on other sites

That may sound good in theory, but if people try to connect to your board and cant access it, its 1 of 2 things. You have turned it off, or you forgot your installer, and then in that case they may just go and reinstall your forum.



I like the idea of moving it to the security panel, and when there is a security update it loads that page first. +1



Well it would tell them that they needed to remove the install/index.php file or the install directory before they could continue.
Link to comment
Share on other sites

I guess its a question of letting the admin know they have left the installer in play, but not letting anyone else know. That's why it's important that a board not be left too long in it's default state, even if the admin creates five or six accounts and makes spurious posts to give anyone the idea it is a fully installed board actively in use rather than a just installed board so they go looking for the /install/index.php file.

In any case IPB requires the admin to have created a database prior to installation.

I would leave it in the ACP in that case. I now appreciate the subtlety of not advertising the fact to the world that the installer is still there.

Link to comment
Share on other sites

Exactly. Is not deleting it a security risk? Sure. Is it as risky as leaving the CHMOD of conf_global.php at 777? I wouldn't think so. I just think this setting deserves to be on the Security Center page along with all other similar security threats from the files/settings on the board.

Link to comment
Share on other sites

I would go one step further and prohibit use of the board entirely until the install.php file is removed from the installation directory. If people do not understand that an important part of the installation is to remove the installer before going "click to log in" then they really shouldn't be doing the install IMO.


I agree. With vBulletin, you are forced to remove the installation files before you are allowed access to the ACP. This would be a good idea for IPB to adopt, as well.
Link to comment
Share on other sites

I agree. With vBulletin, you are forced to remove the installation files before you are allowed access to the ACP. This would be a good idea for IPB to adopt, as well.



Except that certain ACP functionality requires the Installation files to be present. (With the obvious exception of Index.php)

IPB locks the installation out unless install.lock is removed anyway, and like I said before - if an exploiter is able to remove install.lock, you have bigger problems on your hands than them running the installer.
Link to comment
Share on other sites

Except that certain ACP functionality requires the Installation files to be present. (With the obvious exception of Index.php)



IPB locks the installation out unless install.lock is removed anyway, and like I said before - if an exploiter is able to remove install.lock, you have bigger problems on your hands than them running the installer.

I know that you need the /install/ file. You should be locked out of the ACP for the first time until you remove /index.php, like what vBulletin already does.
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...