Tickets :: Comment on [#14026] Use of raw_data in Horde_Crypt_Blowfish

Search Results: 22 of 151 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: .__ .___..__..__ __ [__) \| \| \|[__)/ ` [__) \| \|__\|\| \\__.
Comment	>> 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?
Attachment
Watch this ticket