RE: Why the index is not used ? - Mailing list pgsql-general
From | ROS Didier |
---|---|
Subject | RE: Why the index is not used ? |
Date | |
Msg-id | 0f723a9063f14e2096eb36e720a8048b@PCYINTPEXMU001.NEOPROD.EDF.FR Whole thread Raw |
Responses |
RE: Why the index is not used ?
|
List | pgsql-general |
Hi Phil Thank you for this recommendation, but I posted on this public list only generic examples that have nothing to do withthe works done in my company. These examples serve me only to discuss about the subject of data encryption and performance My answers to your remarks : >> Why do you need to search by credit card number? << Again, this is just an example. I just want to find a solution to query a column containing encrypted data with good performance. >> one option is to use an encryption function that doesn't salt the data << I am interested. Can you give some examples of these encryption function that doesn't salt the data. Best Regards Didier ROS -----Message d'origine----- De : phil_tnlcz_endecott@chezphil.org [mailto:phil_tnlcz_endecott@chezphil.org] Envoyé : dimanche 7 octobre 2018 21:17 À : ROS Didier <didier.ros@edf.fr>; pgsql-general@lists.postgresql.org Objet : RE: Why the index is not used ? Hello Didier, Your email is didier.ros@edf.fr. Are you working at Electricite de France, and storing actual customers' credit card details? How many millions of them? Note that this mailing list is public; people looking for targets with poor security from which they can harvest credit cardnumbers might be reading it. And after you are hacked and all your customers' credit card details are made public, someone will find this thread. > it's not the best solution, but we have data encryption needs and good > performance needs too. I do not know how to do it except the specified > procedure.. You should probably employ someone who knows what they are doing. Sorry for being so direct, but really... storing large quantities of credit card details is the text book example of somethingthat has to be done correctly. > if anyone has any proposals to put this in place, I'm interested. Why do you need to search by credit card number? If you really really need to do that, then one option is to use an encryption function that doesn't salt the data. Or youcould store part of the number (last 4 digits?), or an unsalted hash of the number, unencrypted and indexed, and thenyou need only to sequentially decrypt (using the salted encryption) e.g. 1/10000 of the card numbers. But there arecomplex security issues and tradeoffs involved here. You probably need to comply with regulations (e.g. "PCI standards")which will specify what is allowed and what isn't. And if you didn't already know that, you shouldn't be doingthis. Good luck, I suppose. Phil. P.S. It seems that you were asking about this a year ago, and got the same answers... Ce message et toutes les pièces jointes (ci-après le 'Message') sont établis à l'intention exclusive des destinataires etles informations qui y figurent sont strictement confidentielles. Toute utilisation de ce Message non conforme à sa destination,toute diffusion ou toute publication totale ou partielle, est interdite sauf autorisation expresse. Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de le copier, de le faire suivre, de le divulguerou d'en utiliser tout ou partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de votre système,ainsi que toutes ses copies, et de n'en garder aucune trace sur quelque support que ce soit. Nous vous remercionségalement d'en avertir immédiatement l'expéditeur par retour du message. Il est impossible de garantir que les communications par messagerie électronique arrivent en temps utile, sont sécuriséesou dénuées de toute erreur ou virus. ____________________________________________________ This message and any attachments (the 'Message') are intended solely for the addressees. The information contained in thisMessage is confidential. Any use of information contained in this Message not in accord with its purpose, any disseminationor disclosure, either whole or partial, is prohibited except formal approval. If you are not the addressee, you may not copy, forward, disclose or use any part of it. If you have received this messagein error, please delete it and all copies from your system and notify the sender immediately by return message. E-mail communication cannot be guaranteed to be timely secure, error or virus-free.
pgsql-general by date: