Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72097
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH8Mpnnu0BqRmb1PmGjQLTWYA0mtGkJdniDbGbD1Nn+Fn30JZw@mail.gmail.com>
References: <CAH8MpnnmKt2byQU8DcWetnK6W7GB9HuF3srea-ECwQ4RRe1SWQ@mail.gmail.com>
	<CAEZPtU7Euu1mQiJ-2n8r9hQjt9ShqRaiQAouP=FSFeV9OVdjwA@mail.gmail.com>
	<CAH8Mpnnu0BqRmb1PmGjQLTWYA0mtGkJdniDbGbD1Nn+Fn30JZw@mail.gmail.com>
Date: Mon, 3 Feb 2014 19:49:33 +0100
Message-ID: <CAEZPtU6HCowgpemN_yi1--TfySZ5N4ck8omdb-O8RmOpfLz+zA@mail.gmail.com>
To: Daniel Lowrey <rdlowrey@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Windows Peer Verification
From: pierre.php@gmail.com (Pierre Joye)

On Mon, Feb 3, 2014 at 7:46 PM, Daniel Lowrey <rdlowrey@gmail.com> wrote:

> The only real question here is this:
>
> ***** Should we ship a CA file? *****
>
> Personally, I say no. If people are going to programmatically use encrypted
> stream transfers they need to at the very least understand the basics of the
> CA system. We shouldn't subsidize insecurity, and it's trivially easy to
> procure a CA file.

We should for the windows binaries and use a script to update it. This
script should be part of the src distros.

I have added the curl ca cert file option because many users requested
it. It is very handy to have the ability to get a uptodate certs file,
especially when the OS one is outdated and cannot be updated (yes, it
happens :).

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org