That's clearly not entirely true as .php is still being processed within /protected. Surely it would be better to fix whatever is actually exploitable? At the moment the pain = complete bustage so no, not really any better than a critical exploitation as far as my end users are concerned.
On 29 September 2010 00:55, Pete Collins <[email protected]> wrote: > > On 9/28/10 5:40 PM, Mycroft Project wrote: >> >> and how does that actually improve security!? > > It allows us to turn php on and off for specific projects like yours. > > It's better to deal w/ the pain now instead of dealing w/ a critical > exploitation. > > --pete > > -- > Pete Collins - Founder, Mozdev Group Inc. > www.mozdevgroup.com > Mozilla Software Development Solutions > tel: 1-719-302-5811 > fax: 1-719-302-5813 > > _______________________________________________ > Project_owners mailing list > [email protected] > https://www.mozdev.org/mailman/listinfo/project_owners > -- Charles Caygill Mycroft Project Owner http://mycroft.mozdev.org _______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
