summaryrefslogtreecommitdiff
path: root/ext/sodium
Commit message (Collapse)AuthorAgeFilesLines
...
| | * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-152-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-152-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Move all testing docs to qa.php.netPeter Kokot2018-10-181-3/+0
| | | | | | | | | | | | | | | | | | | | | The qa.php.net currently includes nice collection of information about tests and how to run them. Instead of maintaining two locations of this information, this patch removes the README.TESTING from the php-src repo. Patch for qa.php.net has been sent separately to that repo.
* | | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-152-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Sync leading and final newlines in source code filesPeter Kokot2018-10-141-1/+0
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | Merge branch 'PHP-7.2' into PHP-7.3Frank Denis2018-10-142-7/+21
|\ \ | |/ | | | | | | | | | | | | * PHP-7.2: ext/sodium: sodium_pad(): do not copy any bytes if the string is empty ext/sodium: Fix sodium_pad() with blocksize >= 256 ext/sodium: Use a correct max output size for base64 decoding ext/sodium: Avoid shifts wider than 32 bits on size_t values
| * ext/sodium: sodium_pad(): do not copy any bytes if the string is emptyFrank Denis2018-10-141-6/+11
| | | | | | | | | | | | Spotted by San Zhang, thanks! Backport from PECL libsodium-php 2.0.13
| * ext/sodium: Fix sodium_pad() with blocksize >= 256Frank Denis2018-10-141-1/+2
| | | | | | | | Backport from PECL libsodium-php 2.0.12
| * ext/sodium: Use a correct max output size for base64 decodingFrank Denis2018-10-142-1/+8
| | | | | | | | | | | | Also handle the case where the function is not available in test. Backport from PECL libsodium-php 2.0.12
| * ext/sodium: Avoid shifts wider than 32 bits on size_t valuesFrank Denis2018-10-141-1/+2
| | | | | | | | Backport from PECL libsodium-php 2.0.10
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2018-09-291-3/+2
|\ \ | |/
| * Fix reflection arguments for sodium_memzero functionJames Titcumb2018-09-291-3/+2
| |
* | Remove unused Git attributes identPeter Kokot2018-07-252-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The $Id$ keywords were used in Subversion where they can be substituted with filename, last revision number change, last changed date, and last user who changed it. In Git this functionality is different and can be done with Git attribute ident. These need to be defined manually for each file in the .gitattributes file and are afterwards replaced with 40-character hexadecimal blob object name which is based only on the particular file contents. This patch simplifies handling of $Id$ keywords by removing them since they are not used anymore.
* | Merge branch 'PHP-7.2'Nikita Popov2018-06-081-0/+1
|\ \ | |/
| * Avoid leaking the urandom fdKeyur Govande2018-06-081-0/+1
| | | | | | | | | | | | When Apache is reloaded, it unloads the extension, but the open file descriptor to /dev/urandom is left hanging around and is leaked. This fixes the bug. Duplicate of https://github.com/jedisct1/libsodium-php/pull/173
| * year++Xinchen Hui2018-01-022-2/+2
| |
* | Avoid useless checks, using zend_string_efree(), in cases where the string ↵Dmitry Stogov2018-05-081-84/+84
| | | | | | | | is known to be a temporary allocated zend_string.
* | Fix: follow the indent of the other configure optionsTom Van Looy2018-02-151-1/+1
| |
* | Use int instead of integer in type errorsGabriel Caruso2018-02-041-1/+1
| | | | | | | | | | | | | | PHP requires integer typehints to be written "int" and does not allow "integer" as an alias. This changes type error messages to match the actual type name and avoids confusing messages like "must be of the type integer, integer given".
* | year++Xinchen Hui2018-01-022-2/+2
| |
* | Move constants into read-only data segmentDmitry Stogov2017-12-141-1/+1
|/
* Revert "Revert "ext/sodium: pwhash: do not warn on low parameters""Frank Denis2017-11-291-23/+38
| | | | | | | This reverts commit a1845b7fdb5916b0951146ca18bb67ca83854733. Revert "Revert "ext/sodium: throw exceptions instead of errors"" This reverts commit 31d221f9c72f0d0322c84907c5d89a4464667244.
* Revert "ext/sodium: pwhash: do not warn on low parameters"Frank Denis2017-11-291-36/+23
| | | | This reverts commit c219991c77e4c68f7d62963e18a1da778de0bbe0.
* Revert "ext/sodium: throw exceptions instead of errors"Frank Denis2017-11-281-17/+15
| | | | This reverts commit c05cbd1e775fa69ed9939796a908390f2bfb4459.
* ext/sodium: throw exceptions instead of errorsFrank Denis2017-11-281-15/+17
|
* ext/sodium: pwhash: do not warn on low parametersFrank Denis2017-11-281-23/+36
| | | | but raise an explicit error if these are too low
* Fix uninitialized varsAnatol Belski2017-10-231-1/+1
|
* ext/sodium: untab testsFrank Denis2017-10-0214-145/+183
|
* ext/sodium: import secretstream testFrank Denis2017-10-021-0/+61
|
* ext/sodium: sodium_compare() is always availableFrank Denis2017-10-021-3/+0
|
* ext/sodium: fix funky indentationFrank Denis2017-10-021-7/+7
|
* ext/sodium: move pwhash_scrypt() after pwhash()Frank Denis2017-10-021-118/+118
|
* ext/sodium: checks for crypto_box_SEALBYTES are not requiredFrank Denis2017-10-021-4/+0
|
* ext/sodium: explicitly include <string.h>Frank Denis2017-10-021-0/+1
|
* ext/sodium: zend_parse_parameters -> zend_parse_parameters_throwFrank Denis2017-10-021-19/+27
|
* ext/sodium: fix funky indent on zend_parse_parameters_throw() callsFrank Denis2017-10-021-131/+131
|
* ext/sodium: import bindings for secretstreamFrank Denis2017-10-022-0/+256
|
* ext/sodium: add crypto_pwhash_str_needs_rehash()Frank Denis2017-10-022-1/+25
| | | | Also properly define xchacha20poly1305_ietf_keygen()
* ext/sodium: +base64 codecs (timing-safe)Frank Denis2017-10-022-0/+89
|
* ext/sodium: add arginfo definitions that will be required laterFrank Denis2017-10-021-2/+32
| | | | | Don't check for existence of aesgcm symbols, since we only support libsodium >= 1.0.8
* ext/sodium: sort prototypesFrank Denis2017-10-021-24/+20
|
* ext/sodium: fix pwhash_argon2i testFrank Denis2017-10-011-2/+2
|
* ext/sodium: call crypto_pwhash_argon2id() explicitly if requiredFrank Denis2017-09-261-5/+17
|
* ext/sodium: avoid tautological comparisonsFrank Denis2017-09-261-2/+1
|
* ext/sodium: signing empty messages is fineFrank Denis2017-09-261-1/+1
|
* ext/sodium: avoid negations on unsigned valuesFrank Denis2017-09-211-1/+1
|
* ext/sodium: throw an exception if only the prefix of a hex string is validFrank Denis2017-09-191-2/+8
|
* Improve sodium "invalid parameters" error messagesSammy Kaye Powers2017-09-071-13/+41
|