Re: encryption

[David C. Hicks]

I would tend to agree with this.  It is highly unlikely that you'll 
change algorithms once your application is deployed.  It certainly 
doesn't make much sense to mix algorithms unless you're seriously 
paranoid.  Using a FieldConversion object also keeps your application 
developer (you may be the same person) from having to do the encryption 
work.  One possible drawback is that you may want to use different 
encryption keys for different fields.  Using a FieldConversion would 
make that more difficult.  Just something to think about.

I found when doing some encryption work earlier this year that Oracle's 
RAW column type was the right choice in order to store the data after 
encryption.  You also have to make sure that you provide enough space 
for any padding bytes that your encryption algorithm may add to the data.

Dave

Conall O'Raghallaigh wrote:

I would think separate converter classes the various algorithms, but I
haven't gotten far enough into it to know what makes the most sense.
-Conall

 

 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]