[Tickets #14026] Re: Use of raw_data in Horde_Crypt_Blowfish_Openssl

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: https://bugs.horde.org/ticket/14026
------------------------------------------------------------------------------
  Ticket           | 14026
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Use of raw_data in Horde_Crypt_Blowfish_Openssl
  Warteschlange    | Horde Framework Packages
  Typ              | Bug
-Status           | Unconfirmed
+Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2015-09-17 20:43) hat geschrieben:

> Can be replaced with $raw_data = false to force the use of base64  
> format? Of course in both encrypt/decrypt operations

No, because the API of Horde_Crypt_Blowfish defines the input and  
output to be binary and portable.

We can probably change the logic in Horde_Session#get() to first check  
if the data is encrypted, and only check for the NOT_SERIALIZED flag  
if it is not. Do you by chance have some example data that produces  
leading NULs during encryption, so we can create a unit test?