Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87638
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain kelunik.com from 81.169.146.221 cause and error)
MIME-Version: 1.0
In-Reply-To: <55C15F1B.9010401@gmail.com>
References: <CAKws9z1fatmSR2YLaeBn0zVv-s3iwCj7OUKjW949QC0L_VndpA@mail.gmail.com>
	<55C0685E.2070202@gmail.com>
	<CAKws9z3gBf+_0cSPvo3Sh4NAxuPRZT5EbQoqbvhnLxpyjY4F8g@mail.gmail.com>
	<55C15F1B.9010401@gmail.com>
Date: Wed, 5 Aug 2015 06:53:43 +0200
Message-ID: <CANUQDCi--e9mv+R1fHoeP5AhmVw80heKgPzkLiM=mu_P531bfg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Scott Arciszewski <scott@paragonie.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7bacbed6ee5fd3051c892fb0
Subject: Re: [PHP-DEV] PHP 7.1 Cryptography Projects
From: me@kelunik.com (Niklas Keller)

--047d7bacbed6ee5fd3051c892fb0
Content-Type: text/plain; charset=UTF-8

>
> So my question here is - how important task is switching crypto backends
> easily? Moreover, what would be the reason for me, as an app developer,
> to target more than one crypto backend? I can see why I may want to
> target mysql and say, SQL server - these two platforms have different
> advantages, etc. But if OpenSSL works for my app, why would I need to
> support any other backend? Do I have a chance of a client saying "oh, we
> don't run apps using OpenSSL, only libsodium"? Abstraction is a nice
> thing, but in this case I'm not sure about the added value. Of course,
> if crypto library goes out of support - like mcrypt - it can be handy,
> but given that each library probably will have own peculiarities, I'm
> not sure abstraction would allow for clean switch anyway.


Yes, it's important if libraries are abandoned or you want to switch to
another
backend, because you finally decided you don't want to trust OpenSSL
anymore.

Regards, Niklas

--047d7bacbed6ee5fd3051c892fb0--