From owner-freebsd-ports@FreeBSD.ORG Wed May 8 12:23:27 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2659386; Wed, 8 May 2013 12:23:27 +0000 (UTC) (envelope-from feld@feld.me) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by mx1.freebsd.org (Postfix) with ESMTP id 71115B3F; Wed, 8 May 2013 12:23:26 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BE4491F78; Wed, 8 May 2013 08:23:25 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 08 May 2013 08:23:25 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:date:subject:cc:mime-version :content-transfer-encoding:from:message-id; s=mesmtp; bh=hkyfTBC gYTLRm3fQXWXp7ClkYdA=; b=DdqybYcBNRhFGlF6WO+gpRlBCVfSOYPNHHCcWH2 E6MW6GzCHsL9XaDyDXKtFuFx/uzh1uFjiQMjPniwHfTTjrlgB0CuhqlE1xl/dds4 AjD5Pybl3jDXpAAM/CvuUYCV4JwKs3gX486Rf4njrXJBAqnoS9nFV5eq0wEyZ6jR ZJjU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:date:subject:cc :mime-version:content-transfer-encoding:from:message-id; s= smtpout; bh=hkyfTBCgYTLRm3fQXWXp7ClkYdA=; b=FgNYuCviGOuxPl+iBbEP k8KeEOHokQbaGXd1DrDrlr5YJsZ1FAmqBDoPpC4PeQiDVz90SJd1hgc+53WuWC3F FAhdT5jNKgXeKITHcJKcfLEiaDACb8STXjdV2r97RmPEGAFowWUCskQr+/atvzVm TaN80m7FfhiokeWO0jzK0Pk= X-Sasl-enc: C7fkmeK33WTshMBMmfKYoNS5/6XYT+IaasDAplbxYDco 1368015801 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 05E40C8000E; Wed, 8 May 2013 08:23:20 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "freebsd-ports@FreeBSD.org" Date: Wed, 08 May 2013 07:23:20 -0500 Subject: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: User-Agent: Opera Mail/12.14 (FreeBSD) Cc: "ale@freebsd.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 12:23:27 -0000 I'm hoping someone out there can help come up with a solution or a clever patch because right now the only alternative I see is an extremely painful patch to the ports tree that I'd never be able to successfully maintain at my place of employment. The problem is that the way FreeBSD handles PHP -- complete modularization -- breaks the FTP module. The FTP module cannot be built with support for FTPS unless it is built statically into PHP along with OpenSSL. You can test this yourself by running the following command: php -r 'if(function_exists('ftp_ssl_connect')) {echo "ftp_ssl_connect exists\n";} else {echo "ftp_ssl_connect does not exist\n";}' As documented here: http://php.net/manual/en/function.ftp-ssl-connect.php > Note: Why this function may not exist >ftp_ssl_connect() is only available if both the ftp module and the > OpenSSL > support is built statically into php, this means that on Windows this > function will be undefined in the official PHP builds. To make this > functionavailable on Windows you must compile your own PHP binaries. If you look at Debian and Redhat Linux distros there is no php5-ftp or php5-openssl package. It's statically built into the base php5 package. Even Gentoo appears to be doing it right because the ebuild just lets you choose what options you want and it compiles the entire thing statically. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-lang/php/php-5.3.23.ebuild?view=markup I've already submitted a PR, but I'd like some further input from the community. I'm really in a sticky situation here because we were forced to require FTPS everywhere and now things like Wordpress' self-upgrading capability is broken. If we could flip everyone to SFTP I'd gladly do it, but there are too many obstacles in the way for that to become a reality. In short, is anyone out there interested in trying to figure out how to get the FTP module to build with the SSL capability? (Vinnie here has the same reaction I do: https://bugs.php.net/bug.php?id=38951)