User tests: Successful: Unsuccessful:
Pull Request resolves # .
This PR fixes a mode-validation typo in the OpenSSL AES adapter that caused valid ecb input to be rejected, adds a regression test, and aligns related AES documentation comments.
Functional fix in OpenSSL.php:90 mode allowlist now accepts ecb instead of the misspelled ebc.
Regression test added in OpenSSLTest.php:30.
###Discovery/Triage
This issue was initially identified during a Semgrep-assisted review and then manually validated.
php -l libraries/src/Encrypt/AES/OpenSSL.php
php -l tests/Unit/Libraries/Cms/Encrypt/AES/OpenSSLTest.php
###Actual result BEFORE applying this Pull Request
###Expected result AFTER applying this Pull Request
Please select:
Documentation link for guide.joomla.org:
No documentation changes for guide.joomla.org needed
Pull Request link for manual.joomla.org:
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
| Category | ⇒ | Libraries Unit Tests |
| Title |
|
||||||
| Labels |
Added:
Unit/System Tests
Updates Requested
bug
PR-5.4-dev
|
||
| Labels |
Removed:
Updates Requested
|
||
@mateeaaaaaaa Please confirm the AI policy by checking the check box (replacing the space inside the squared brackets by a capital X).
P.S.: ... and apply my 3 change suggestions.
I’ve allowed myself to apply my review suggestions.
@mateeaaa As mentioned in my previous comment, I have allowed myself to apply some code style suggestions.
There is one more thing you could do. Could you remove the new unit test (file tests/Unit/Libraries/Cms/Encrypt/AES/OpenSSLTest.php) from your PR?
It might have been useful for testing your PR, but besides that it is not really useful as it tests just this one case and uses reflection. Unit tests should test the public interface of a class. That might not be possible for the issue fixed by your PR.
Besides this, your PR is fine.
| Labels |
Added:
Updates Requested
|
||
| Category | Libraries Unit Tests | ⇒ | Libraries |
@mateeaaa As mentioned in my previous comment, I have allowed myself to apply some code style suggestions.
There is one more thing you could do. Could you remove the new unit test (file
tests/Unit/Libraries/Cms/Encrypt/AES/OpenSSLTest.php) from your PR?It might have been useful for testing your PR, but besides that it is not really useful as it tests just this one case and uses reflection. Unit tests should test the public interface of a class. That might not be possible for the issue fixed by your PR.
Besides this, your PR is fine.
As there was no reaction by the author, I've allowed myself to apply the requested change (removal of the not useful new unit test).
| Labels |
Removed:
Unit/System Tests
Updates Requested
|
||
| Status | Pending | ⇒ | Ready to Commit |
RTC as it has 3 approvals by maintainers and cannot really be tested by end users.
RTC as it has 3 approvals by maintainers and cannot really be tested by end users.
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-05-09 14:40:19 |
| Closed_By | ⇒ | richard67 | |
| Labels |
Added:
RTC
|
||
@mateeaaaaaaa Please confirm the AI policy by checking the check box (replacing the space inside the squared brackets by a capital X).
P.S.: ... and apply my 3 change suggestions.