Re: PHP 7.1 Cryptography Projects
| From: | Stanislav Malyshev | Date: | Wed, 05 Aug 2015 00:10:26 +0000 |
| Subject: | Re: PHP 7.1 Cryptography Projects | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-87631@lists.php.net to get a copy of this message | ||
Hi!
> We're still discussing the DSN string for the constructor. These are
> what the options look like, currently:
I think it's better to separate the arguments. I understand why PDO
makes such strings - there can be all kinds of options, and it's hard to
configure - i.e. in ini files - if it's not a single string. However, I
think in this case it's less of a concern, and while composing this
string it's too easy to make a mistake with bad consequences.
> * "openssl" should use openssl in a secure, sane default
That's kind of open-ended... Secure, sane default to do what?
> Version and configuration information (not what is passed, but what is
> used) will be stored in the first few bytes of ciphertext output.
That means new cyphertext format. Which makes these functions
incompatible with every other encryption/decryption functions out there
(i.e., if you talk to Java app using these functions, you'd have to
implement your own decryption routines in Java too). Is that really a
good idea?
--
Stas Malyshev
smalyshev@gmail.com