RE: encryption
Date: Tue, 19 Mar 2013 11:38:09 -0500
Message-ID: <3DC440E2338A24439D527C2E64E1ECBCA854EB_at_deeds.pti-nps.com>
Fair point - the encrypted data is stored as RAW in the database, but at that point you might as well not rely on DBMS_CRYPTO for ongoing operations. You can certainly do your decryption AND encryption in the application (although DBMS_CRYPTO might still be useful for backfilling existing fields).
Thanks,
T. J.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Andy Klock
Sent: Tuesday, March 19, 2013 11:30 AM
To: TJ Kiernan
Cc: Zelli, Brian; gints.plivna_at_gmail.com; oracle-l_at_freelists.org
Subject: Re: encryption
On Tue, Mar 19, 2013 at 11:46 AM, TJ Kiernan <tkiernan_at_pti-nps.com> wrote:
> DBMS_CRYPTO is server-side only (encrypting data at rest). If you're
> looking to encrypt SQL*Net traffic, you're going to need Advanced
> Security, which IIRC costs 1/4 a license (and EE).
>
> Thanks,
> T. J.
>
>
That's not necessarily true. DBMS_CRYPTO contains many of the same old algos that which can be decrypted in several programming languages.
http://docs.oracle.com/cd/E11882_01/appdev.112/e16760/d_crypto.htm#BJFFAJCC
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Tue Mar 19 2013 - 17:38:09 CET