Feeling Lucky
?
?
[#13591] - Update the crypto library to composer version
- Closed
- 14 Jan 2017
- Medium
- Build: 4.0-dev
- # 13591
- Diff
- wilsonge:crypto-upgrade
User tests: Successful: Unsuccessful:
Summary of Changes
Makes Joomla's crypt library use the latest version of the crypto library and removes our old version. Note that we already have this library in composer indirectly via the framework crypt package - so that's why the files aren't being installed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | External Library Libraries |
wilsonge
- comment
- 14 Jan 2017
OK Works for me
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-01-14 21:30:37 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
?
|
||
I wouldn't do this.
Right now, we have the 1.x version of this package as a non-Composer dependency as
JCryptCipherCryptoand the 2.x version as a Composer dependency asJoomla\Crypt\Cipher\Crypto. https://github.com/defuse/php-encryption/blob/master/docs/UpgradingFromV1.2.md implies that you need to deal with changes in the package to keep using your encrypted data when upgrading from 1.x to 2.x so I would suggest leaving this alone (probably just markJCryptCipherCryptoand the 1.x package integration as deprecated for removal in 5.0).