Thinking about this a little bit. (BTW - I am going to use keychain to refer to both platforms equivalent)
If the system is running client server - the keys would need to be stored (and retrieved from) the server's keychain, and this is/would be fine, as long as it was insured that keychain was backed up AND recoverable in case of disk or other hardware failure. However, if the system were to be merged with an engine, or simply run in 4D standalone storing the keys in keychain would make the app not portable, and the key pair to unencrypted the data would be tied to a specific machine, and again the issue of recoverability of the keychain data comes into play. Any thoughts? Chip On Mon, 1 Apr 2019 07:04:36 -0600, John DeSoi via 4D_Tech wrote: > On the Mac one option is to script storing the private key in the > Keychain with LAUNCH EXTERNAL PROCESS. Type "man security" Terminal > to see the command line interface options. > > John DeSoi, Ph.D. > > >> On Mar 31, 2019, at 10:54 PM, Chip Scheide via 4D_Tech >> <[email protected]> wrote: >> >> I was planning on keeping the keys in the data file... but I can see >> that might be an issue. >> Any other ideas on where/how to keep the keys, given the above? > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** --------------- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
