The approach that I would take here is ... secure the channel. Use certificates to authenticate the users (and to secure the communications with each). Use existing standard protocols to do this, not one that you have rolled. Put the information on a highly-secured server which will only communicate with bearers of currently-valid credentials. The information that passes through the secured channel can be plaintext, since it passes between parties with mutually-assured identities. The database files are encrypted using a key known only to the server: these services are already readily-available in any major server. I would advocate avoiding use of deterministic encryption altogether, because I do not think it will ever provide the data-security and data-integrity that you need.
I fail to see why you should be having to “roll your own anything” to accomplish this... This is hardly an atypical or novel requirement.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||