Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50330 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17752 invoked from network); 18 Nov 2010 10:07:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Nov 2010 10:07:55 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@gmail.com X-Host-Fingerprint: 209.85.216.170 mail-qy0-f170.google.com Received: from [209.85.216.170] ([209.85.216.170:57521] helo=mail-qy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/F2-32235-9FAF4EC4 for ; Thu, 18 Nov 2010 05:07:54 -0500 Received: by qyk36 with SMTP id 36so1778783qyk.8 for ; Thu, 18 Nov 2010 02:07:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:reply-to :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; bh=k98lpJ/fqlVKCrpW8a3jM/qApW0PvTic/eJP2rYVM5Y=; b=tyuI08yW9a52PRphHoB4izRetXalqL5+JCo3MA6oYCjQDoXPrDo/tk4/eCNp3CpCdX QhdUuhDc5+7zkjBoAlo8a8bVt/J8ej3kbA89OERKDFuuYd33zyjYnvP4Cb9sWfWplMlc InAbXLQfNjsw2LQy5G+nzK5VskgfDAvN77Xdo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; b=fbgvnE2E6jBK3lln7FPXLBQbyYmunDUJIo7+/XeyGiHonZqK/JzcBrSQYnsPXf84+R pDVQtUo68evTRAUaphWLTdI8m+KTbhFVxeSJTUqqqdG/UrH8aYDILCa0QfZMUuAuYDb7 Wba+ksJZloYYYOfJ0bcOxkb/VR9Yv/R7lZs7s= Received: by 10.229.229.83 with SMTP id jh19mr408809qcb.130.1290074870259; Thu, 18 Nov 2010 02:07:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.100.84 with HTTP; Thu, 18 Nov 2010 02:07:30 -0800 (PST) Reply-To: RQuadling@googlemail.com In-Reply-To: References: Date: Thu, 18 Nov 2010 10:07:30 +0000 Message-ID: To: Kalle Sommer Nielsen Cc: Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Magic quotes in trunk From: rquadling@gmail.com (Richard Quadling) On 17 November 2010 16:08, Kalle Sommer Nielsen wrote: > Greetings > > I wanted to raise this topic before we go Alpha with trunk, regarding > our beloved magic_quotes feature. There seems to be mixed opinions > regarding it so I thought I would take it up for discussion. > > We have advised people not to use magic_quotes, register_globals and > the like for years, and they were marked as deprecated in 5.3.0+ if > activated through their php.ini directives. Yet magic_quotes still is > set to "On" in 5.3.0. I think its worth we either remove the feature > or disable it in trunk as its a security related feature. Lets have a > look at what each of those options means: > > Removing magic_quotes): > Means we will remove the feature entirely in the source, we will throw > an E_CORE_ERROR if activated so people who have it enabled are forced > to disable it and make their applications work without magic_quotes. > This creates a minor issue for the hosts that simply disable it and > have their customers applications run without them which can create a > security risk for them, although it should be fairly limited. The > functions to check for magic_quotes_runtime should however stay for BC > to avoid applications that run on multiple versions of PHP from doing: > if(function_exists('...') && ...) > > Disabling them): > This will help to disable the spread of magic_quotes even more, and it > can safely be removed in the next major version of PHP. > > > My personal vote here goes towards removing them entirely. > > > What are your inputs on this matter? > > -- > regards, > > Kalle Sommer Nielsen > kalle@php.net Certainly +1 for removal, but wasn't there some discussion a LONG while ago about when this should be? I would have thought that anything deprecated would best be removed at the next major release. So that makes it gone for V6 - when ever that may be. Richard -- Richard Quadling Twitter : EE : Zend @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY