Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3667 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96962 invoked from network); 31 Jul 2003 16:40:33 -0000 Received: from unknown (HELO mail.cpmd.com) (209.15.204.205) by pb1.pair.com with SMTP; 31 Jul 2003 16:40:33 -0000 Received: from [82.36.17.153] (helo=fatcuban) by mail.cpmd.com with esmtp (Exim 3.12 #1 (Debian)) id 19iGTg-0001di-00 for ; Thu, 31 Jul 2003 16:40:32 +0000 Message-ID: <009801c35782$b551fc80$1400000a@fatcuban> To: References: <059101bffadb$28a33670$1400000a@fatcuban> <005201c35777$6812e7a0$1400000a@fatcuban> Date: Thu, 31 Jul 2003 17:41:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300 Subject: Re: [PHP-DEV] upload compromises From: root@fatcuban.com ("skate") sorry, unfortunatly i haven't got a full solution, just a suggestion. i don't know how difficult any of this would be to implement, but i feel that it could benefit the community by adding a little extra security. i do fully understand that it's not gonna be 100% fool proof, or security proof. very little is when you have any kind of user input. but every little bit does help. thanks for entertaining the idea with me tho :)