Re: Security::cipher() and mysqldump

Note that one string is double the length of the other.

Ôd§5ð£ïäì vs Ã"`ª5ñ¦ïìíµM ....

And UTF-8 typically takes 16 bits and ascii 8......

Just a hunch but I'd bet you should be able to make a PHP function to
convert them back.

b

On Tue, 2012-04-10 at 15:52 -0300, Thiago Belem wrote:
> Are you using the same Security.cipherSeed and Security.salt?
>
> --
> Thiago Belem
> Desenvolvedor
> Rio de Janeiro - RJ - Brasil
>
> thiagobelem.net
> contato@thiagobelem.net
>
> Skype / gTalk » thiago.belem.web
> LinkedIn » br.linkedin.com/in/thiagobelem/pt
> Assando Sites, curso de CakePHP » assando-sites.com.br
>
>
> On Tue, Apr 10, 2012 at 15:42, etipaced <kevindecapite@gmail.com>
> wrote:
> Thanks for the help. Unfortunately, it didn't work. My
> database, table and fields are all UTF-8. The ciphered values
> import from the dump file into the table correctly. The
> problem is that I believe they are incorrect in the dump file
> itself. Meaning, mysqldump did not export them properly and
> somehow changed the encoding. I don't know if I can do
> anything to convert the odd ciphers back to what they should
> look like.
>
>
> Here's an example of a "good" cipher. It's a value that was
> created on the server and stored directly into the database
> table. In other words, it has not been exported/imported:
>
>
> Ôd§5ð£ïäì
>
>
> Here's an example of a "bad" cipher from my backup file
> (generated by mysqldump):
>
>
> Ã"`ª5ñ¦ïìíµM
>
>
> As you can see, the format and pattern are totally different.
> I'm unable to decipher the second example which means a loss
> of 450+ field values.
>
>
>
>
> On Monday, April 9, 2012 10:24:50 AM UTC-7, etipaced wrote:
> I know there have been discussions surrounding the
> issue of suhosin with Cake's Security::cipher()
> method. I am in the process of discontinuing usage of
> Cake's ciphering functionality due to this issue.
> However, I do have existing data that has been
> ciphered already. My problem is that the data has been
> exported (via mysqldump) and then imported back into
> the same database (on the exact same server). What I
> didn't notice until after the fact, is that the
> ciphered data now looks different than it originally
> did. As a result, it's essentially corrupted. Is there
> anything I can do as I no longer have the originally
> created ciphered data, but only mysqldumps of it.
>
> --
> Our newest site for the community: CakePHP Video Tutorials
> http://tv.cakephp.org
> Check out the new CakePHP Questions site
> http://ask.cakephp.org and help others with their CakePHP
> related questions.
>
>
> To unsubscribe from this group, send email to
> cake-php+unsubscribe@googlegroups.com For more options, visit
> this group at http://groups.google.com/group/cake-php
>
>
>
> --
> Our newest site for the community: CakePHP Video Tutorials
> http://tv.cakephp.org
> Check out the new CakePHP Questions site http://ask.cakephp.org and
> help others with their CakePHP related questions.
>
>
> To unsubscribe from this group, send email to
> cake-php+unsubscribe@googlegroups.com For more options, visit this
> group at http://groups.google.com/group/cake-php

--
Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org
Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions.

To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php