Tickets :: [#10950] encryptKey parameter is not a valid callback.

6.0.0-alpha14

7/1/25

Summary	encryptKey parameter is not a valid callback.
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Resolved
Priority	2. Medium
Owners	slusarz (at) horde (dot) org
Requester	vilius (at) lnk (dot) lt
Created	02/01/2012 (4899 days ago)
Due
Updated	02/01/2012 (4899 days ago)
Assigned	02/01/2012 (4899 days ago)
Resolved	02/01/2012 (4899 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

02/01/2012 07:57:10 PM	Git Commit	Comment #9	Reply to this comment
Changes have been made in Git (refs/heads/develop): commit 67213172a90e95e3a409dc461c81b4159f10a269 Author: Michael M Slusarz <slusarz@horde.org> Date: Wed Feb 1 11:41:32 2012 -0700 [mms] Fix objects where the password is not being encrypted (~~Bug #10950~~). .../Imap_Client/lib/Horde/Imap/Client/Base.php \| 2 +- framework/Imap_Client/package.xml \| 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) http://git.horde.org/horde-git/-/commit/67213172a90e95e3a409dc461c81b4159f10a269

02/01/2012 06:45:42 PM	Michael Slusarz	Comment #8 Assigned to Michael Slusarz State ⇒ Resolved	Reply to this comment
Not sure why but encryptKey here is ALWAYS null. The strange thing is that with 1.3.2 the exception is not thrown. I was correct before - we didn't change anything regarding encryptKey. And you are wrong - with 1.3.2 the exception was always being thrown. The difference is that the Exception type changed, and we were not catching the new exception type, so it was bubbling to the main program and causing a fatal error. Fixed code so we catch ANY exception in the future, since any error indicates we can not encrypt the password. Released Horde_Imap_Client 1.4.2 fixing this issue.

02/01/2012 06:45:01 PM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git (refs/heads/master): commit 67213172a90e95e3a409dc461c81b4159f10a269 Author: Michael M Slusarz <slusarz@horde.org> Date: Wed Feb 1 11:41:32 2012 -0700 [mms] Fix objects where the password is not being encrypted (~~Bug #10950~~). .../Imap_Client/lib/Horde/Imap/Client/Base.php \| 2 +- framework/Imap_Client/package.xml \| 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) http://git.horde.org/horde-git/-/commit/67213172a90e95e3a409dc461c81b4159f10a269

02/01/2012 06:17:15 PM	vilius (at) lnk (dot) lt	Comment #6	Reply to this comment
Not sure why but encryptKey here is ALWAYS null. The strange thing is that with 1.3.2 the exception is not thrown. I'm not running APC or suhosin. Now that you told to clear all sessions I did so, but it didn't help.

02/01/2012 06:03:10 PM	Michael Slusarz	Comment #5	Reply to this comment
I can verify with Jan. Nothing has changed regarding encryptKey during this time period. Don't believe me: do this in the Imap_Client directory in a git checkout: git diff horde_imap_client-1.3.2..horde_imap_client-1.4.1 . Not to mention that this is precisely the kind of thing that a developer would /probably/ notice immediately. Have you cleared your APC caches on your PHP server? Or disabled suhosin (if you are using that)? Or made sure all of your sessions have been destroyed?

02/01/2012 03:37:20 PM	ben (at) catbird (dot) net	Comment #4	Reply to this comment
I can confirm that. Downgrading Imap_Client to 1.3.2 solved the problem. Also confirmed here. 1.3.32 works, 1.4.x throws the error.

02/01/2012 02:19:12 PM	Jan Schneider	State ⇒ Feedback Priority ⇒ 2. Medium

02/01/2012 02:18:34 PM	Jan Schneider	Comment #3	Reply to this comment
After Imap_Client upgrade from 1.3.2 to 1.4.1 Horde/IMP is broken. HORDE encryptKey parameter is not a valid callback. [pid 6832 on line 201 of "/usr/share/pear/Horde/Imap/Client/Base.php"] What is it, if not a callback? It's been a callback since this code path has been called in IMP 5.0. The only difference is that we throw a different exception at this place in Horde_Imap_Client.

02/01/2012 11:44:57 AM	horde (at) mbox (dot) tinloaf (dot) de	Comment #2	Reply to this comment
I can confirm that. Downgrading Imap_Client to 1.3.2 solved the problem.

02/01/2012 09:27:03 AM	vilius (at) lnk (dot) lt	Comment #1 State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Summary ⇒ encryptKey parameter is not a valid callback. Type ⇒ Bug Priority ⇒ 3. High	Reply to this comment
After Imap_Client upgrade from 1.3.2 to 1.4.1 Horde/IMP is broken. HORDE encryptKey parameter is not a valid callback. [pid 6832 on line 201 of "/usr/share/pear/Horde/Imap/Client/Base.php"]