| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| | |
* PHp-5.4:
news for bug #61421
commit for php bug 61421 enabling SHA2 and RMD160 for openssl signature verification
|
| |
| |
| |
| | |
enabling SHA2 and RMD160 for openssl signature verification
|
| |
| |
| |
| |
| | |
This reverts commit b5b8ea1050837fba5a6cee55e41b4574ed64158e.
Looks like we don't have agreement yet on this for 5.4. Let's keep it in 5.5 for now.
|
| |
| |
| |
| |
| |
| |
| | |
like a spell."
This reverts commit bccd1e672fabc3c788e93075221d47d9f077b167.
Looks like we don't have agreement yet on this for 5.4. Let's keep it in 5.5 for now.
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
* 5.4:
Rename openssl_pkcs5_pbkdf2_hmac() to something that doesn't sound like a spell.
Add PBKDF2 support via openssl()
Conflicts:
ext/openssl/openssl.c
|
| |
| |
| |
| |
| | |
Summary:
Stas pointed out that this is named pretty poorly. Go for openssl_pbkdf2()
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Summary:
No easy way to put these in the hash extension since we don't really support optional
parameters to certain algorithms. Implemented in openssl for now since it has it already
and is pretty stable.
Only SHA1 is confirmed to work as an algorithm but openssl has a parameter so it can be
changed in the future.
Will backport to 5.4 potentially with Stas' approval.
Test Plan:
Ran newly added tests which came from RFC 6070
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Summary:
No easy way to put these in the hash extension since we don't really support optional
parameters to certain algorithms. Implemented in openssl for now since it has it already
and is pretty stable.
Only SHA1 is confirmed to work as an algorithm but openssl has a parameter so it can be
changed in the future.
Will backport to 5.4 potentially with Stas' approval.
Test Plan:
Ran newly added tests which came from RFC 6070
|
| |
| |
| |
| |
| | |
Summary:
Stas pointed out that this is named pretty poorly. Go for openssl_pbkdf2()
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
* 5.4:
Add PBKDF2 support via openssl()
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Summary:
No easy way to put these in the hash extension since we don't really support optional
parameters to certain algorithms. Implemented in openssl for now since it has it already
and is pretty stable.
Only SHA1 is confirmed to work as an algorithm but openssl has a parameter so it can be
changed in the future.
Will backport to 5.4 potentially with Stas' approval.
Test Plan:
Ran newly added tests which came from RFC 6070
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
false.
|
| |
| |
| |
| |
| | |
another encoding. 5.4 only as this implies a BC break.
|
| | |
|
| |
| |
| |
| | |
function but as this function was badly introduced in the 1st place, we have to fix the bad things here instead, pls do not revert again, bad idea.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Lets discuss this on internals first. We're advertising something from the OpenSSL library
and then subverting it with another Windows OS call.
What are the implications of this? Should we make this available in ext/standard/ instead?
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the default size for the case of a variable key length cipher.
The result is a key of 448 bits being passed to the blowfish algorithm would be truncated to 128 bit.
Also fixed an error in the zend_parse_parameters() having an invalid character being used.
|
| |
| |
| |
| | |
openssl's version
|
| |
| |
| |
| | |
and not TS)
|
| |
| |
| |
| |
| |
| |
| |
| | |
null byte in the middle))
# The tests will be fixed in the next commits
|
| |
| |
| |
| |
| |
| | |
For using mcrypt / openssl interchangeabley managing your own padding is the only solution.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
false.
|
| |
| |
| |
| |
| | |
another encoding. 5.4 only as this implies a BC break.
|
| | |
|
| |
| |
| |
| | |
function but as this function was badly introduced in the 1st place, we have to fix the bad things here instead, pls do not revert again, bad idea.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Lets discuss this on internals first. We're advertising something from the OpenSSL library
and then subverting it with another Windows OS call.
What are the implications of this? Should we make this available in ext/standard/ instead?
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the default size for the case of a variable key length cipher.
The result is a key of 448 bits being passed to the blowfish algorithm would be truncated to 128 bit.
Also fixed an error in the zend_parse_parameters() having an invalid character being used.
|
| |
| |
| |
| | |
openssl's version
|
| |
| |
| |
| | |
and not TS)
|
| |
| |
| |
| |
| |
| |
| |
| | |
null byte in the middle))
# The tests will be fixed in the next commits
|
|/
|
|
|
|
| |
For using mcrypt / openssl interchangeabley managing your own padding is the only solution.
|
|
|
|
|
| |
that way in our code as well.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
windows versions
|
| |
|
| |
|