|Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread|
|Messages 1 to 3 of 3 total|
|Fri, Oct 23 2009 9:42 AM||Permanent Link|
Can we have a utility to change this please, even if its just from the default of elevatesoft to a new value.
To explain why. I'm in progress with an app that will eventually be distributed as freeware in a single user incarnation (I'll ship it with elevatesoft as the localencryption password). If someone wants to buy a licence they'll get a unique licence key which will also be used as the encryption key so I need a painless way of altering from the default to the new value. I'll be preventing any of the tables being encrypted whilst the default is in use so I don't need to bother about that.
Part of the definition of painless is not having to reverse engineer the database. I really don't want to have to build that into the app. On the other hand if it involves starting a process and then having to go for a 3 course meal while it runs that's fine.
|Sat, Oct 24 2009 7:10 AM||Permanent Link|
Tim Young [Elevate Software]
Elevate Software, Inc.
<< Can we have a utility to change this please, even if its just from the
default of elevatesoft to a new value. >>
I'll see what I can do. It's a little dicey because there currently isn't
any way to say "prevent someone else from opening the configuration file",
so it is something that could take place while other sessions are accessing
the same configuration file that is being converted to using a different
encryption password. I know that this doesn't apply in your case, but I
can't code these things with assumptions like that in place.
|Sat, Oct 24 2009 7:32 AM||Permanent Link|
Its a very valid concern, and one I'm wrestling with at the moment. Having thrown everyone off how do you keep them off. I'm seeing what I can do with EXPORT/IMPORT (which I'll use for other purposes as well) as a way round changing the encryption.