Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81801 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87089 invoked from network); 4 Feb 2015 10:14:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2015 10:14:11 -0000 Authentication-Results: pb1.pair.com smtp.mail=jan@horde.org; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=jan@horde.org; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain horde.org does not designate 82.98.68.218 as permitted sender) X-PHP-List-Original-Sender: jan@horde.org X-Host-Fingerprint: 82.98.68.218 fra.ammma.de Linux 2.6 Received: from [82.98.68.218] ([82.98.68.218:33617] helo=fra.ammma.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/A6-55046-CE0F1D45 for ; Wed, 04 Feb 2015 05:14:09 -0500 Received: from ammma.de (fra2-hb [192.168.1.12]) by fra.ammma.de (Postfix) with ESMTPS id E36825B04CC for ; Wed, 4 Feb 2015 11:13:58 +0100 (CET) Received: from mail.ammma.net (ns.ammma.mil [192.168.110.1]) by ammma.de (8.11.6/8.11.6/AMMMa AG) with ESMTP id t14ADwF14737 for ; Wed, 4 Feb 2015 11:13:58 +0100 Received: from neo.wg.de (hydra.ammma.mil [192.168.110.1]) by mail.ammma.net (Postfix) with ESMTP id 8B56D40CE0 for ; Wed, 4 Feb 2015 11:13:58 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by neo.wg.de (Postfix) with ESMTP id 9CADA190A1D6 for ; Wed, 4 Feb 2015 11:14:02 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at wg.de Received: from neo.wg.de ([127.0.0.1]) by localhost (neo.wg.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ec9mp5Uh9UZn for ; Wed, 4 Feb 2015 11:13:58 +0100 (CET) Received: from neo (localhost [IPv6:::1]) by neo.wg.de (Postfix) with ESMTPS id ED0B5190A1B7 for ; Wed, 4 Feb 2015 11:13:57 +0100 (CET) Received: from port-212-202-167-178.static.qsc.de (port-212-202-167-178.static.qsc.de [212.202.167.178]) by yunosh.horde.org (Horde Framework) with HTTP; Wed, 04 Feb 2015 11:13:57 +0100 Date: Wed, 04 Feb 2015 11:13:57 +0100 Message-ID: <20150204111357.Horde.f9QXyF6QU-jKQIPfOVdg3g1@yunosh.horde.org> To: internals@lists.php.net References: <0d436102ec3afeeb91673e2d30c64de4.squirrel@webmail.klapt.com> <54D1C176.6000107@gmail.com> In-Reply-To: User-Agent: Horde Application Framework 5 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline Subject: Re: [PHP-DEV] [RFC][VOTE] Removal of dead or not yet PHP7 ported SAPIs and extensions From: jan@horde.org (Jan Schneider) Zitat von Anatol Belski : > Hi Stas, > > On Wed, February 4, 2015 07:51, Stanislav Malyshev wrote: >> Hi! >> >> >>> And at list this one living native PHP implementation >>> https://github.com/horde/horde/tree/master/framework/Imap_Client/ (and >>> more library links in the older thread link above). >> >> This is part of Horde with 9 listed dependencies and 9 suggested ones, >> and probably also sub-dependencies. It is much less convenient than having >> imap right here when you run PHP. And looks like on top of that it lists >> PHP 7 as not supported. >> I'm sure there are other imap implementations, but I wouldn't be that >> quick in throwing out one that a lot of people may use. -- >> Stas Malyshev >> smalyshev@gmail.com >> > Horde is being developed by a some ISP, so it's mostlikely gonna support > PHP7, even if not already. But this is actually what one can say regarding > PHP7 compatibility with any scripts at the current stage. FWIW Horde is an open source project and not developed by any ISP. Furthermore we're actively testing against PHP 7 and already detected (and reported) a few bugs an regressions in master. Not that this matters for this discussion, just for completeness. > For security tickets - there are still some on mitre, NVD and others. > > The point with ext/imap being available "now and here" instead of the > userland implementation is of course good. However removing it has the > same reasons like f.e. removing ext/regex or Apache 1.x SAPI. Letting it > be there, unmaintained, is kinda of a black hole. And every day it grows. > > That's why my point is rather - link to some userland implementation > instead of shipping "worky" stuff in the unknown security state. Same > actually for mcrypt. Probably the same motivation can be attributed to the > unavailability of libc-client and mcrypt in RHEL6. > > Regards > > Anatol > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php -- Jan Schneider The Horde Project http://www.horde.org/ https://www.facebook.com/hordeproject