[Tickets #12443] Re: After upgrading to Horde 5.1.1 syncing contacts fails

noreply at bugs.horde.org noreply at bugs.horde.org
Fri Jul 12 20:48:04 UTC 2013


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

Ticket URL: http://bugs.horde.org/ticket/12443
------------------------------------------------------------------------------
  Ticket             | 12443
  Updated By         | gandalfmagic at libero.it
  Summary            | After upgrading to Horde 5.1.1 syncing contacts fails
  Queue              | Synchronization
  Version            | Git master
  Type               | Bug
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


gandalfmagic at libero.it (2013-07-12 20:48) wrote:

This commit solved the issue for me too.
Thanks!

Anyway, regardind this error I've found my log full of this messages:

Jul 12 22:10:36 isengard HORDE: [horde] PHP ERROR: openssl_encrypt():  
Using an empty Initialization Vector (iv) is potentially insecure and  
not recommended [pid 20393 on line 44 of  
"/usr/share/php/Horde/Crypt/Blowfish/Openssl.php"]
Jul 12 22:10:37 isengard HORDE: [kronolith] PHP ERROR:  
openssl_encrypt(): Using an empty Initialization Vector (iv) is  
potentially insecure and not recommended [pid 20393 on line 44 of  
"/usr/share/php/Horde/Crypt/Blowfish/Openssl.php"]
Jul 12 22:10:37 isengard HORDE: [imp] PHP ERROR: openssl_encrypt():  
Using an empty Initialization Vector (iv) is potentially insecure and  
not recommended [pid 20393 on line 44 of  
"/usr/share/php/Horde/Crypt/Blowfish/Openssl.php"]
Jul 12 22:10:39 isengard HORDE: [gollem] PHP ERROR: openssl_encrypt():  
Using an empty Initialization Vector (iv) is potentially insecure and  
not recommended [pid 20393 on line 44 of  
"/usr/share/php/Horde/Crypt/Blowfish/Openssl.php"]

Well, I was testing an unofficial PHP version on that server  
(5.4.17RC1 from a PPA).
I reverted to official 5.3.2 and the problem seems solved.



> In your horde.log you have:
>
> Jul 12 11:57:33 isengard HORDE:  1.  
> Horde_Rpc_ActiveSync->getResponse()  
> /srv/www/applications/horde/rpc.php:156  2.  
> Horde_ActiveSync->handleRequest()  
> /usr/share/php/Horde/Rpc/ActiveSync.php:141  3.  
> Horde_ActiveSync->authenticate()  
> /usr/share/php/Horde/ActiveSync.php:736  4.  
> Horde_Core_ActiveSync_Driver->authenticate()  
> /usr/share/php/Horde/ActiveSync.php:561  5.  
> Horde_Core_Auth_Application->authenticate()  
> /usr/share/php/Horde/Core/ActiveSync/Driver.php:181  6.  
> Horde_Core_Auth_Application->_setAuth()  
> /usr/share/php/Horde/Core/Auth/Application.php:138  7.  
> Horde_Registry->setAuth()  
> /usr/share/php/Horde/Core/Auth/Application.php:639  8.  
> Horde_Registry->setAuthCredential()  
> /usr/share/php/Horde/Registry.php:2489  9. Horde_Secret->write()  
> /usr/share/php/Horde/Registry.php:2381 10.  
> Horde_Crypt_Blowfish->encrypt() /usr/share/php/Horde/Secret.php:75  
> 11. Horde_Crypt_Blowfish_Openssl->encrypt()  
> /usr/share/php/Horde/Crypt/Blowfish.php:110 12. openssl_encrypt()  
> /usr/share/php/Horde/Crypt/Blowfish/Openssl.php:44 13. Horde_Error
>
>
> No idea where this is coming from, do you?





More information about the bugs mailing list