Closed (won't fix)
Project:
Drupal core
Version:
6.x-dev
Component:
filter.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Feb 2010 at 19:36 UTC
Updated:
18 Aug 2010 at 22:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
bjaspan commentedThe filter system changed a lot in D7. I found this problem on D6. I'm not sure if it still exists on D7 or not.
Patch attached for D6. Not sure if this is really the right solution.
Comment #2
sunLooks good to me.
Comment #3
gábor hojtsyLooking at the D7 code, it seems to return an empty array if the format requested did not exist, so there should be no infinite recursion from filter_list_format() itself. Committed.
Comment #5
David_Rothstein commentedHm, I'm pretty sure this replaced an infinite recursion with a security hole - is that really an improvement? :)
Granted, if they find themselves in the situation where the default format doesn't exist, they've managed to do something to seriously break their site anyway, and we don't have to support that. So it's not an actual hole, but I think it is still a definite security weakness to allow this - I'd rather see their site break in an obvious way, rather than in a silent way that can lead it to get hacked.
I think we should either roll this back or possibly replace it with throwing an exception or something, rather than silently returning an empty list of filters for the deleted format.
Comment #6
gábor hojtsyOk, rolled back for now.
Comment #7
sunSince the whole auto-fallback mechanism in D6 is wrong in the first place, I don't see another way than throwing an exception or letting it recurse infinitely. Both equals boom, so any effort here is not really worth the effort, especially since this applies to D6 only.