I'm adding a facility into an app for users to set / alter the encryption password.

The process I'll be following is:

1. unencrypt any encrypted tables

2. go through the configuration database and extract the CreateSQL for: Modules, TextFilters, WordGenerators, Users, Roles, UserRoles, databases,Jobs, Stores (for Users get their passwords and replace <Password> with the real thing)

3. extract the permissions from configuration

4. close the TEDBSession component

5. delete the EDBConfig.EDBCfg file

6. alter the encryption password for the TEDBSession component and open

7. use the data extracted from the old configuration to create: Modules, TextFilters, WordGenerators, Users, Roles, UserRoles, databases,Jobs, Stores

8. use the data extracted from the old configuration to set the permissions

9. re-encrypt the tables that were deleted to start with

I would be delighted if someone could tell me an easier way


Roy Lambert

Roy,

This forum has been pretty dead since Christmas, not sure what's going on. So I decided to chime in.

That app you're writing should really be included with EDBMgr because everyone will want to change their encryption pw one time or another and it is a PIA to do it manually. So congrats on making the attempt. Make sure you have a couple of backups before proceeding and maybe hang a rabbit's foot on the monitor as well.

You may find this thread useful, http://www.elevatesoft.com/forums?action=view&category=edb&id=edb_general&page=1&msg=15503#15503 if you haven't seen it already.

Let us know how you make out.

Barry

Roy Lambert wrote:

I'm adding a facility into an app for users to set / alter the encryption password.

The process I'll be following is:

1. unencrypt any encrypted tables

2. go through the configuration database and extract the CreateSQL for: Modules, TextFilters, WordGenerators, Users, Roles, UserRoles, databases,Jobs, Stores (for Users get their passwords and replace <Password> with the real thing)

3. extract the permissions from configuration

4. close the TEDBSession component

5. delete the EDBConfig.EDBCfg file

6. alter the encryption password for the TEDBSession component and open

7. use the data extracted from the old configuration to create: Modules, TextFilters, WordGenerators, Users, Roles, UserRoles, databases,Jobs, Stores

8. use the data extracted from the old configuration to set the permissions

9. re-encrypt the tables that were deleted to start with

I would be delighted if someone could tell me an easier way


Roy Lambert

Barry


>That app you're writing should really be included with EDBMgr because everyone will want to change their encryption pw one time or another and it is a PIA to do it manually. So congrats on making the attempt. Make sure you have a couple of backups before proceeding and maybe hang a rabbit's foot on the monitor as well.

It's my simple opinion that EDBManager should NEVER be distributed with an app. The potential for the average user to screw up with it is just to great.

>Let us know how you make out.

Its working

Roy

I agree with Barry that it would be useful to have a command built into EDBMgr to allow a developer to change the encryption password on all the elements in a database. Maybe Tim could plug your code into a new version of EDBMgr??

Roy,


>It's my simple opinion that EDBManager should NEVER be distributed with an app. <
Agreed. But the developer could connect to the user's database remotely and make the changes to the user's database. Or use the utility locally and ship the db back to the user.

>The potential for the average user to screw up with it is just to great.<
As it stands new, "The potential for the average *developer* to go through these steps manually to change the encryption pw, to screw up is just too great".

That's why I think Tim should put it into EDBMgr (provided of course it requires the Administrator password to use it).

Barry

Adam,

<< I agree with Barry that it would be useful to have a command built into
EDBMgr to allow a developer to change the encryption password on all the
elements in a database. Maybe Tim could plug your code into a new version of
EDBMgr?? >>

Got it on the list, just haven't gotten around to it yet.

Tim Young
Elevate Software
www.elevatesoft.com

Barry

>>It's my simple opinion that EDBManager should NEVER be distributed with an app. <
>Agreed. But the developer could connect to the user's database remotely and make the changes to the user's database. Or use the utility locally and ship the db back to the user.
>
>>The potential for the average user to screw up with it is just to great.<
>As it stands new, "The potential for the average *developer* to go through these steps manually to change the encryption pw, to screw up is just too great".

Depends on your interpretation of "screw up". The worst is putting the wrong encryption password in and simply building it into EDBManager doesn't remove that possibility.

>That's why I think Tim should put it into EDBMgr (provided of course it requires the Administrator password to use it).

I think it should be built into ElevateDB (possibly part of an ALTER DATABASE command) and surfaced in ElevateDB.

Roy

>I think it should be built into ElevateDB (possibly part of an ALTER DATABASE command) and surfaced in ElevateDB.<

+1

Barry