RE: Data Encryption -- MIDRANGE-L

Subject: RE: Data Encryption
From: Andy Youens <andy@xxxxxxxxxxxxxx>
Date: Sat, 19 May 2007 09:02:17 +0100
Accept-language: en-US, en-GB
Acceptlanguage: en-US, en-GB
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Tom

Great point to bring up, that's often overlooked.

The Redbook IBM System i Security Guide for IBM i5/OS Version 5 Release 4
http://www.redbooks.ibm.com/abstracts/sg246668.html?Open has good examples of
column encryption in SQL. I know it's for V5.4 but I've used it examples at
V5.3

Regards
Andy Youens | Senior IBM Consultant | formaserve systems ltd
v 01908 609500 | 07770 380276 | http://www.formaserve.com

Larry:

Before settling on a method, keep in mind the various uses the

column value will be put to. For example, will it serve as a foreign
key in any way? Will it be used as an index column?

Encrypting the value might affect how the table is searched and how
it can relate to other tables. These might lead to one method over
another.

Tom Liotta

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.