Hi John
That would be cool, but I am not sure what would be the best option.
Run Only option but you can not open or view the file, but you would still
require the password to Run the file
or maybe
Run without a password and only use the password to edit or view the file?
Maybe someone else has a better idea on this?
Marc
-----Original Message-----
From: John Minyo II
Sent: Monday, August 01, 2011 3:07 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - OUTPUT filename ENCRYPT (Was: Form Timer and Hourly
backups)
At 11:25 AM 08/01/2011, MDRD wrote:
Lets say I have an Owner password of something like ABC123, but on the
Unload All Encrypt I use xyz for my password.
Then the user can Restore the DB by entering the xyz password, but if they
had RBedit could they open the Unload.Dat file then see my Owner password
and learn all me trade secrets? LOL
So, I was thinking of Code locking a restore file that would hide the
Unload password to prevent the above possibility, or am I missing
something?
Marc,
The OUTPUT command has the ability to add a 512-bit encryption
key to a file for security purposes. After using the ENCRYPT
parameter in your OUTPUT command, a prompt is display to enter
a password.
The password must be specified in order to run or edit the file.
Perhaps you would like suggest an enhancement where a "run only"
512-bit encryption key would be used for a file?
Best regards,
John Minyo II
R:BASE Technologies, Inc.
Customer Service
