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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10950
------------------------------------------------------------------------------
  Ticket             | 10950
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | encryptKey parameter is not a valid callback.
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Feedback
+State              | Resolved
  Priority           | 2. Medium
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-02-01 11:45) wrote:

> 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.