-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update used version of phpseclib #394
Comments
What would be the value of phpseclib update? |
I would suggest of using one of the tagged versions. "0.2.2" would be the next bugfix release, so i suggest for starting the value "0.2.x" which uses the last stable version of the "0.2" minor release. If you want to update to the next minor version, i would suggest "0.3.x" its ok to not using a specific commit hash, as during development and maybe even after release, you want to include bugfix releases. For your official release there is still the composer.lock file, which specifies the exact version you targeted on release date. |
@Flyingmana, returning to the initial question. What value do you see in this update? |
Well, back to the question - at least would be nice to remove it from The only place where
The only place where
(currently not published with CE) So, the best option could be to get rid of this library usage by refactoring or use another one. For example, Omnipay is using Guzzle:
|
As magento already uses the library via composer now, this issue would be solved for me. But removing it complete would also be ok I think, as it has a very limited featureset, which mostly has good native replacements. |
Not really loaded via Composer yet, still present in repository code base: https://github.com/magento/magento2/tree/develop/lib/internal/phpseclib |
I see, got confused by https://github.com/magento/magento2/blob/develop/composer.json#L160 |
[Firedrakes] Implementation of data version control in Customer and Quote modules + Bug fixing
@Flyingmana, phpseclib is now upgraded to 0.3.10 version, library was removed from source code and added to composer dependencies. |
This issue appears to have been resolved, so I'm going ahead and closing it. Feel free to reopen if you disagree with this assessment. |
…tication CABPI-81 user authentication
the used version of phpseclib was not updated since magento 1.5, there are a lot of chanegs since. Used version seems to be 19cc43cc1668e179bc4da1782a47d8514e665ff5 / https://github.com/phpseclib/phpseclib/tree/19cc43cc1668e179bc4da1782a47d8514e665ff5
two things to know about.
but you could also use something like this for the start
The text was updated successfully, but these errors were encountered: