New answers tagged

0

Performance is probably being hurt by all the COMMITs and single-row actions. The following should speed it up by order(s) of magnitude. Do a batch of 100 rows at a time A single multi-row INSERT for the the extra table. Use BEGIN...COMMIT around each batch. Since you need to pull the data out, encrypt it, and then put it back in, here are some more ...


0

You're paying the extra price of network IO and there's not a whole lot you can do if you need to remove the encryption (really the key storage/management) from the database. If your MySQL instance is on a Unix host, you can try connecting with a Unix socket file instead of TCP/IP. Just host the app on the same machine during the encryption process, finish ...


2

Since your thumbprint is being returned as a System.String you actually cannot easily convert it to a System.Byte. I have not gotten a full example that you are doing to work completely but will show you how I convert the thumbprint, and it seems to work: $encode = [System.Text.Encoding]::UTF8 $r1 = $encode.GetBytes($thumbprint) $sha = New-Object ...


0

Encryption at rest can't address server breaches, it is only intended to mitigate cases of physical data storage theft, and data access by unauthorised people, e.g. cloud technicians. MariaDB encryption wouldn't be able effectively deal with either, because stealing the drives would effectively provide root access to the system, including access to the ...



Top 50 recent answers are included