encript BIG data php or mysql ?

[Gufo Rosso]

PHP
$gg = string file file_get_contents size is 40 mb max
field = addslashes(gzcompress($gg))

performances are accepted with a dozen people at most if you use
AES_ENCRIPT ?
or agrees to process the data first and stuck already encrypted WITHOUT
use the features of MySQL?

thanks

[Jerry Stuckle]

First of all, you shouldn't be using addslashes() for your data. It's
the wrong function.

Second, ANY encryption you do on a 40 mb file is going to slow your
system down. But which is faster is very dependent on a lot of things,
including your system. You need to test and compare them yourself.

--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstu...@attglobal.net
==================

[Johannes Keßler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

this wil really slow down your system.

If you use php via a webserver, then you will have a memory or timeout really fast.
If you use php as CLI, then you are more safe.

But I think neither php nor mysql are the beste choices for encription.

Use external programms or processes to encrpyt your data and use PHP and MySQL
as the method to display and handle the data for the user.

regards,
johannes keßler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (GNU/Linux)

iEYEARECAAYFAksKQyYACgkQE++2Zdc7Etd2ngCeKFAdwA2wYtcTby2bbh0Ag+ca
gRwAnA+xWr9kLnUK6+Ks3Q1eVXysGidG
=HnLD
-----END PGP SIGNATURE-----

[Axel Schwenke]

Gufo Rosso <spaaaaa...@libero.it> wrote:
> PHP
> $gg = string file file_get_contents size is 40 mb max
> field = addslashes(gzcompress($gg))
>
> performances are accepted with a dozen people at most if you use
> AES_ENCRIPT ?

Why don't you try it? AES is typically pretty fast (it was designed
to allow fast software implementation). I guess the bigger problem
will the sheer amount of data. 40M is beyond typical "max_upload" or
"max_memory_per_request" limits.

> or agrees to process the data first and stuck already encrypted WITHOUT
> use the features of MySQL?

I *guess* this is better done in the web/applicationserver. At least
if you want to be able to scale out. But of course the much more
important (in fact the only important) question is: what is the threat
scenario? Does it really leave a choice where to encrypt and where to
have the key?

XL