This repository has been archived by the owner on Jan 29, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ZF2015-10 patch
- Loading branch information
Showing
5 changed files
with
127 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,85 @@ | ||
# Changelog | ||
|
||
All notable changes to this project will be documented in this file, in reverse chronological order by release. | ||
|
||
## 2.5.2 - 2015-11-23 | ||
|
||
### Added | ||
|
||
- Nothing. | ||
|
||
### Deprecated | ||
|
||
- Nothing. | ||
|
||
### Removed | ||
|
||
- Nothing. | ||
|
||
### Fixed | ||
|
||
- **ZF2015-10**: `Zend\Crypt\PublicKey\Rsa\PublicKey` has a call to `openssl_public_encrypt()` | ||
which used PHP's default `$padding` argument, which specifies | ||
`OPENSSL_PKCS1_PADDING`, indicating usage of PKCS1v1.5 padding. This padding | ||
has a known vulnerability, the | ||
[Bleichenbacher's chosen-ciphertext attack](http://crypto.stackexchange.com/questions/12688/can-you-explain-bleichenbachers-cca-attack-on-pkcs1-v1-5), | ||
which can be used to recover an RSA private key. This release contains a patch | ||
that changes the padding argument to use `OPENSSL_PKCS1_OAEP_PADDING`. | ||
|
||
Users upgrading to this version may have issues decrypting previously stored | ||
values, due to the change in padding. If this occurs, you can pass the | ||
constant `OPENSSL_PKCS1_PADDING` to a new `$padding` argument in | ||
`Zend\Crypt\PublicKey\Rsa::encrypt()` and `decrypt()` (though typically this | ||
should only apply to the latter): | ||
|
||
```php | ||
$decrypted = $rsa->decrypt($data, $key, $mode, OPENSSL_PKCS1_PADDING); | ||
``` | ||
|
||
where `$rsa` is an instance of `Zend\Crypt\PublicKey\Rsa`. | ||
|
||
(The `$key` and `$mode` argument defaults are `null` and | ||
`Zend\Crypt\PublicKey\Rsa::MODE_AUTO`, if you were not using them previously.) | ||
|
||
We recommend re-encrypting any such values using the new defaults. | ||
|
||
## 2.4.9 - 2015-11-23 | ||
|
||
### Added | ||
|
||
- Nothing. | ||
|
||
### Deprecated | ||
|
||
- Nothing. | ||
|
||
### Removed | ||
|
||
- Nothing. | ||
|
||
### Fixed | ||
|
||
- **ZF2015-10**: `Zend\Crypt\PublicKey\Rsa\PublicKey` has a call to `openssl_public_encrypt()` | ||
which used PHP's default `$padding` argument, which specifies | ||
`OPENSSL_PKCS1_PADDING`, indicating usage of PKCS1v1.5 padding. This padding | ||
has a known vulnerability, the | ||
[Bleichenbacher's chosen-ciphertext attack](http://crypto.stackexchange.com/questions/12688/can-you-explain-bleichenbachers-cca-attack-on-pkcs1-v1-5), | ||
which can be used to recover an RSA private key. This release contains a patch | ||
that changes the padding argument to use `OPENSSL_PKCS1_OAEP_PADDING`. | ||
|
||
Users upgrading to this version may have issues decrypting previously stored | ||
values, due to the change in padding. If this occurs, you can pass the | ||
constant `OPENSSL_PKCS1_PADDING` to a new `$padding` argument in | ||
`Zend\Crypt\PublicKey\Rsa::encrypt()` and `decrypt()` (though typically this | ||
should only apply to the latter): | ||
|
||
```php | ||
$decrypted = $rsa->decrypt($data, $key, $mode, OPENSSL_PKCS1_PADDING); | ||
``` | ||
|
||
where `$rsa` is an instance of `Zend\Crypt\PublicKey\Rsa`. | ||
|
||
(The `$key` and `$mode` argument defaults are `null` and | ||
`Zend\Crypt\PublicKey\Rsa::MODE_AUTO`, if you were not using them previously.) | ||
|
||
We recommend re-encrypting any such values using the new defaults. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters