Irrespective of this discussion, a single salt value for all you entries
is discouraged. It's better to have one salt value per entry. Some
algorithms even embed the salt in the encrypted value itself so that
everything is stored in a single column.
In an ideal world, you would keep the salts in a
Sure, its been discussed before. In numerous forms.
However, I am not sure exactly how a generic @Encrypt solution is
supposed to work. Not sure exactly what you are thinking here, so hard
to say.
On 02/25/2013 12:15 PM, Brett Meyer wrote:
> Have encryption capabilities in ORM ever been consi
