Subject | Re: [ib-support] Re: crypted data |
---|---|
Author | Ann W. Harrison |
Post date | 2003-02-04T16:48:39Z |
At 09:58 AM 2/3/2003 +0000, duilio_fos <irel_llc@...> wrote:
the configuration file and a few other odds and ends, is done
through routines called PIO_xxx. They're found in modules called
unix.c, win32.c, vms.c, etc., one for each I/O style.
You could certainly intercept those operations so the data would
be encrypted as it went to disk and decrypted as it came back.
But that doesn't solve anything if your system manager can use
the server, since the data will be presented to him decrypted.
Alternately, you could encrypt data at the client side, though
that makes indexing and things like that work badly.
Regards,
Ann
www.ibphoenix.com
We have answers.
>If the same low level Read/Write functions are used along the wholeWell, yes and no. The physical I/O, except for sort files reading
>program (both for table data and keys), the effort should be minimal.
the configuration file and a few other odds and ends, is done
through routines called PIO_xxx. They're found in modules called
unix.c, win32.c, vms.c, etc., one for each I/O style.
You could certainly intercept those operations so the data would
be encrypted as it went to disk and decrypted as it came back.
But that doesn't solve anything if your system manager can use
the server, since the data will be presented to him decrypted.
Alternately, you could encrypt data at the client side, though
that makes indexing and things like that work badly.
Regards,
Ann
www.ibphoenix.com
We have answers.