Why is that?

Comments

damien tournoud’s picture

Status: Active » Needs review
StatusFileSize
new4.34 KB

Here is a patch.

dries’s picture

Status: Needs review » Fixed

Committed. Thanks DamZ.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

David_Rothstein’s picture

Status: Closed (fixed) » Active

Hm, this doesn't look right to me... It seems like this change prevents IP address blocking from working on update.php altogether?

We can turn it off during the D6->D7 upgrade, but once someone is running full D7, the IP address blocking should start working again (as was the case with the code that this replaced).

damien tournoud’s picture

Hum. True, it does prevent IP address blocking from update.php altogether. I would be happy if someone can find another solution.

damien tournoud’s picture

Priority: Normal » Critical

This is a blocker, now.

David_Rothstein’s picture

I wonder if something similar to the old method would work (try to bootstrap to the correct phase, then catch any exceptions)?

However, I seem to remember from another issue that exception handling in update.php isn't currently working correctly at all.... So possibly this issue is one we should return to later, once update.php is overall less broken.

chx’s picture

Status: Active » Fixed

there is no ACCESS in bootstrap anymore.

David_Rothstein’s picture

Title: DRUPAL_BOOTSTRAP_ACCESS doesn't exist anymore, but is still an explicit bootstrap step » DRUPAL_BOOTSTRAP_ACCESS changes cause IP address blocking to not work on update.php
Status: Fixed » Active

This still valid... retitling to accurately reflect the current issue described above.

chx’s picture

Status: Active » Postponed (maintainer needs more info)

rgrep BOOTSTRAP_ACCESS *
chx@veyron:/var/www/drupal$

David_Rothstein’s picture

Title: DRUPAL_BOOTSTRAP_ACCESS changes cause IP address blocking to not work on update.php » IP address blocking does not work on update.php
Status: Postponed (maintainer needs more info) » Active

Better :)

chx’s picture

Status: Active » Closed (won't fix)

update has its own access control.

David_Rothstein’s picture

Status: Closed (won't fix) » Active

@chx, this is a bug and an unintentional regression. Every page in Drupal has its own access control, and update.php is no different - but the intended behavior is that IP address blocking prevents the page from being bootstrapped or accessed in any way. This is how it works in Drupal 6, and how it worked in Drupal 7 before this issue.

It is possible that we can downgrade this from "critical" - it's hard to imagine a scenario where this would lead to total disaster. But it should be fixed.

catch’s picture

Priority: Critical » Normal

Downgrading, would be nice to fix. Would be nicer to remove ip address blocking from core 'cos it's a big mess.

trevorleenc’s picture

Status: Active » Needs review

#1: 583008-kill-bootstrap-access.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 583008-kill-bootstrap-access.patch, failed testing.

Celine Bessa’s picture

Status: Needs work » Needs review

#1: 583008-kill-bootstrap-access.patch queued for re-testing.

Status: Needs review » Needs work

The last submitted patch, 583008-kill-bootstrap-access.patch, failed testing.

  • Dries committed d92389a on 8.3.x
    - Patch #583008 by Damien Tournoud: DRUPAL_BOOTSTRAP_ACCESS doesn't...

  • Dries committed d92389a on 8.3.x
    - Patch #583008 by Damien Tournoud: DRUPAL_BOOTSTRAP_ACCESS doesn't...

  • Dries committed d92389a on 8.4.x
    - Patch #583008 by Damien Tournoud: DRUPAL_BOOTSTRAP_ACCESS doesn't...

  • Dries committed d92389a on 8.4.x
    - Patch #583008 by Damien Tournoud: DRUPAL_BOOTSTRAP_ACCESS doesn't...

  • Dries committed d92389a on 9.1.x
    - Patch #583008 by Damien Tournoud: DRUPAL_BOOTSTRAP_ACCESS doesn't...

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.