×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Note that I'm not saying that a trigger is good or bad for this encryption requirement, but a trigger does at least represent user code that can make intelligent decisions. The trigger could for instance interrogate the call stack to determine if a trusted application is accessing the data. If so decrypt, if not leave encrypted. You would of course also need to provide the same logic in the update/write trigger.
"Mark S. Waterbury" <mark.s.waterbury@xxxxxxx> wrote: But that would totally defeat the purpose of encrypting the data in
certain fields, wouldn't it? Once such a "read trigger" was in place, if
it could decrypt the data and return that data in the buffer, then any
program that accesses (reads) the file (even DSPPFM, etc.) would then
see the unencrypted data! :-o
M. Lazarus wrote:
Bruce,
Are there any plans that you know of to allow changing a read
trigger buffer? This limitation is a *major* barrier to retrofitting
encryption onto existing databases.
-mark
This mailing list archive is Copyright 1997-2024 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.
midrange.com
