<?xml version="1.0" encoding="windows-1252"?>
<node id="877383" title="Re: Deterministic asymmetric encryption [Crypt::RSA]" created="2010-12-15 16:34:27" updated="2010-12-15 16:34:27">
<type id="11">
note</type>
<author id="647953">
sundialsvc4</author>
<data>
<field name="doctext">
&lt;p&gt;
The approach that I would take here is ... secure the &lt;em&gt;channel.&lt;/em&gt; &amp;nbsp; Use certificates to authenticate the users (and to secure the communications with each). &amp;nbsp; Use existing standard protocols to do this, not one that you have rolled. &amp;nbsp; Put the information on a highly-secured server which will only communicate with bearers of currently-valid credentials. &amp;nbsp; The information that passes through the secured channel can be plaintext, since it passes between parties with mutually-assured identities. &amp;nbsp; The database files are encrypted using a key known only to the server: &amp;nbsp; these services are already readily-available in any major server. &amp;nbsp; 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.
&lt;/p&gt;&lt;p&gt;
I fail to see why you should be having to &amp;ldquo;roll your own &lt;em&gt;anything&amp;rdquo;&lt;/em&gt; to accomplish this... &amp;nbsp; This is hardly an atypical or novel requirement.
&lt;/p&gt; </field>
<field name="root_node">
877274</field>
<field name="parent_node">
877274</field>
</data>
</node>
