rfc:builtincrypt
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| rfc:builtincrypt [2010/03/24 17:30] – created joey | rfc:builtincrypt [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Request for Comments: | + | ====== Request for Comments: |
| * Version: 1.0 | * Version: 1.0 | ||
| * Date: 2010-03-18 | * Date: 2010-03-18 | ||
| Line 13: | Line 13: | ||
| ==== Pros ==== | ==== Pros ==== | ||
| - | - It will simplify the m4 files for the crypt() extension. | + | |
| - | - It will provide consistent behaviour for all users of PHP. | + | - It will provide consistent behaviour for all users of PHP. |
| - | - It is internally consistent with other, similar decisions such as bundling our own timezone database and versions of various hashing algorithms. | + | - It is internally consistent with other, similar decisions such as bundling our own timezone database and versions of various hashing algorithms. |
| - | - The crypt() documentation has recently been dramatically improved, but only documents the built-in algorithms. An effort to maintain a list of possible system-level incompatibilities would probably be prohibitive. | + | - The crypt() documentation has recently been dramatically improved, but only documents the built-in algorithms. An effort to maintain a list of possible system-level incompatibilities would probably be prohibitive. |
| - | - Prevent the filing of bugs when different systems use different crypt() | + | - Prevent the filing of bugs when different systems use different crypt() |
| ==== Cons ==== | ==== Cons ==== | ||
| - | - Some systems vendors have previously shown resistance to PHP preferring its bundled versions of facilities the OS provides | + | |
| - | - ??? | + | - ??? |
| ===== Changelog ===== | ===== Changelog ===== | ||
rfc/builtincrypt.1269451815.txt.gz · Last modified: 2017/09/22 13:28 (external edit)