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	> Horde_Crypt_Blowfish_Openssl uses $raw_data = true in encrypt/decrypt > operations, so the result can be any binary string, even a string > starting with \0 at the beginning. > > That causes issues like in Horde_Session, where values starting with > \0 are considered NOT_SERIALIZED and are returned unencrypted > (https://github.com/horde/horde/blob/master/framework/Core/lib/Horde/Session.php#L355) > > Can be replaced with $raw_data = false to force the use of base64 > format? Of course in both encrypt/decrypt operations > > >
Attachment
Watch this ticket