Fork me on GitHub

Feedback  Bottom

Go to page [-1] 1 - 2:

  • 2) But both the existence of install.php and the existence of upgrade.php could make your installation vulnerable and should only be used in isolated environments right? Thats why i think it doesn't make sence to have an option to ignore the installer check but to keep warning that upgrade.php should be removed.

    3) My fault, i mean the option to enable/disable the check. Not the warning message itself.
  • 2. Actually, neither should now present a great security risk since they both require admin logon to use. The main risk is probably in potentially revealing what version of PostNuke you are running (or that you are running PostNuke at all

    3. This sounds sensible to me - perhaps you could submit a feature request?

    --
    itbegins.co.uk - Zikula Consulting

    birtwistle.me.uk - Personal Blog


    Please read the Support Guide

Go to page [-1] 1 - 2:

  • 0 users

This list is based on users active over the last 60 minutes.