Re: Encrypting data Was: Securing tape backup drive

[rob@xxxxxxxxx]

Good question.  And the links I sent earlier touch on that, a little.

Keep in mind, that you do meet the requirements that the data is 
encrypted.  And it is encrypted using a "standard", which carries more 
weight than some homegrown that some of us have tried.  Anyone browsing 
the tape for patterns like '123-45-6789' or 9 digit numbers (packed or 
zoned) sure wouldn't find it.

1 - Never put the source on the production machine.  We don't.
2 - Save the programs on a different tape than the data.
3 - Consider not leaving any debug information on stuff with the password 
imbedded.
4 - Consider leaving the password constructed in a service program that 
people must call to use.  Then again, you could have someone, like my 
coworker, who executes it, get's the parameter back, and publishes it to 
the whole department.

For read only you could do something like:
> create view rob/vickerduh as 
   (Select mykey, decrypt_char(myssn,'Ben123') as DisplaySSN 
    from rob/vicker) 
  View VICKERDUH created in ROB. 
> select * from rob/vickerduh 
....+....1....+....2....+...
        MYKEY   DISPLAYSSN 
            1   289-46-8832 
********  End of data  *****



Rob Berendt