Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65555
Return-Path: <pierrick@webstart.fr>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 91390 invoked from network); 1 Feb 2013 15:50:31 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 1 Feb 2013 15:50:31 -0000
Authentication-Results: pb1.pair.com smtp.mail=pierrick@webstart.fr; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=pierrick@webstart.fr; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain webstart.fr from 74.125.82.170 cause and error)
X-PHP-List-Original-Sender: pierrick@webstart.fr
X-Host-Fingerprint: 74.125.82.170 mail-we0-f170.google.com  
Received: from [74.125.82.170] ([74.125.82.170:47975] helo=mail-we0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id FC/D5-41663-544EB015 for <internals@lists.php.net>; Fri, 01 Feb 2013 10:50:30 -0500
Received: by mail-we0-f170.google.com with SMTP id z53so3051259wey.15
        for <internals@lists.php.net>; Fri, 01 Feb 2013 07:50:26 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:x-received:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type:x-gm-message-state;
        bh=WXZ+fjZulZbsCdTW65CjkSsBRyKjPk0xIrUsAEGzeWI=;
        b=mUUaOndXtPPCXb+aCV8gStOBYDsOpE15n4QeJoH6GORU14+YTJURxHsxfr2U6OxWbh
         3xmP7iuA7V5zJ/sNv4bMTYkx8ASEnMj4BUI9gT2njwyCVxxGbUjElaVlwd4ci3bn1eOF
         qWgt9Icr3YAfYV36XmefKLzJ7G/4THoKU5NXRbitRlHfCGbCqEUYY4YsX4UkFRKU69j3
         HlbxAMRvacRvle9Tmv+5cV8oy0ni4+e1LiPP1zCTZuyOQm2OuL85BvoV2zcDfYV50dXA
         3D9YfpN0hkU+tQe/2v9GQITHtuif+ljrxnO3J0Qem9BkGP43KsmU7BjMzxmRZVjY6dZ/
         h7hA==
MIME-Version: 1.0
X-Received: by 10.194.177.199 with SMTP id cs7mr22689924wjc.41.1359733826681;
 Fri, 01 Feb 2013 07:50:26 -0800 (PST)
Received: by 10.180.84.195 with HTTP; Fri, 1 Feb 2013 07:50:26 -0800 (PST)
In-Reply-To: <5106D92C.6020709@sugarcrm.com>
References: <50FC9AC5.9070407@sugarcrm.com>
	<5106D92C.6020709@sugarcrm.com>
Date: Fri, 1 Feb 2013 10:50:26 -0500
Message-ID: <CAOfKkdR013mwtLqgEisnCg_t9n-OKBQeOAcqAmce+8wopbCcZg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013d11c2ba79df04d4abb3ea
X-Gm-Message-State: ALoCoQm5wWPOiNUE5x9F5zN5Y/q88z5ws8t5oE9frQknTJiM7vI+APXNtN0/2nO2iofWmsyRqaYk
Subject: Re: [PHP-DEV] Re: [VOTE] CURLFile uploading API
From: pierrick@webstart.fr (Pierrick Charron)

--089e013d11c2ba79df04d4abb3ea
Content-Type: text/plain; charset=ISO-8859-1

Hi Stas,

I'm not against it but, just being curious, what are those security reasons
?

Thanks
Pierrick

On 28 January 2013 15:01, Stas Malyshev <smalyshev@sugarcrm.com> wrote:

> Hi!
>
> > I've started a vote on CURLFile RFC:
> > https://wiki.php.net/rfc/curl-file-upload#vote
> >
> > Please vote.
>
> Looks like the feature has been approved almost anonymously, so I'll be
> proceeding with merging the pull soon. I'm also planning adding __wakeup
> there that blocks unserializing CURLFile, for security reasons, please
> tell me if anyone thinks it's not good. Also, if anyone has
> comments/suggestions/additions to it, you are welcome to voice them.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--089e013d11c2ba79df04d4abb3ea--