Closed (fixed)
Project:
AES encryption
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
14 Jul 2011 at 09:50 UTC
Updated:
10 Feb 2015 at 15:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dan_lennox commentedPatch supplied.
Comment #2
dan_lennox commentedOK this is still an issue but my fix is completely wrong.
Comment #3
dan_lennox commentedActual issue was being caused by $string = base64_decode($string); being called after the test for "empty" instead of before. Patch supplied.
Comment #4
easyfit commentedI'll leave it to lee20 to apply the patch, but I just want to say nice catch and thanks for looking into this! It's been a standing issue for some time
Comment #5
dan_lennox commentedNo worries. Thanks for the handy module!
Comment #6
dan_lennox commentedWhoops forgot to change status.
Comment #7
EvanDonovan commentedAre you sure this is the correct fix? Seems counter-intuitive not to check first.
Also, tracking for 7.x.
Comment #8
EvanDonovan commentedComment #9
dpovshed commentedIf someone interested in having this fixed - please do code review.
Comment #10
AshwinB commentedAfter applying the patch, the warning still shows up, just with different text.. Now it says "Tried to decrypt an empty string.". After applying the patch, the warning gets logged multiple times during each login. Any suggestions?
Comment #11
dpovshed commented@Amaster123, thank you for testing this!
Comment #13
dpovshed commentedI checked patch in comment #3 and it worked fine to me to solve this minor problem.
Maybe I overlook somethhing and any of you have more sophisticated use-cases - feel free to report in details and reopen issue.
Patch was adopted and committed, thanks @dan_lennox !
Tested with code: