3 ms·
Seems fair enough to me, though the article could do with a lead-in that explains what's being protected, the premise that the database server is a separate mac
by tyingq 9y ago
Seems fair enough to me, though the article could do with a lead-in that explains what's being protected, the premise that the database server is a separate machine, etc.
Protecting the client side would be a completely different approach. Outboard/upstream tokenization or something. If it's directly serving up the sensitive data, there's no real way to leverage encryption for protection there.
- CiPHPerCoder 9y ago> Seems fair enough to me, though the article could do with a lead-in that explains what's being protected, the premise that the database server is a separate machine, etc. Okay, I've added a section that spells this out explicitly and unambiguously. https://paragonie.com/blog/2017/05/building-searchable-encrypted-databases-with-php-and-sql#our-threat-model https://paragonie.com/blog/2017/05/building-searchable-encry...