Hi,

this is the first time I have to encrypt some tables and I don't
understand how it works.

1. I create the table and set encrypted = true
2. I know that there is only one password used by the engine.

How can I change this password so that nobody is able to open the table
using EDBManager without knowing the correct password? At the same time
I have to work with the tables by using EDBManager.

In the ng's I read that I can change a session's password. After doing
so, I cannot open the session any more.
(You can use a custom encryption password in the EDB Manager.  Just include
this line in the edbmgr.ini file here

Please help me understandig this.

Thanks Uli

Uli,

<< How can I change this password so that nobody is able to open the table
using EDBManager without knowing the correct password? At the same time I
have to work with the tables by using EDBManager.

In the ng's I read that I can change a session's password. After doing so,
I cannot open the session any more. (You can use a custom encryption
password in the EDB Manager.  Just include this line in the edbmgr.ini file
here>>

If you are using a custom encryption password, then you need to create the
configuration file/database catalog/table files using the same encryption
password, or else you will receive an error.   I would create a new session
with the new encryption password, and then run a reverse-engineered script
from the first session against the new session/database (after first
creating the database using CREATE DATABASE).

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim ,

> If you are using a custom encryption password, then you need to create the
> configuration file/database catalog/table files using the same encryption
> password, or else you will receive an error.   I would create a new session
> with the new encryption password, and then run a reverse-engineered script
> from the first session against the new session/database (after first
> creating the database using CREATE DATABASE).

Hmmm. Not that easy. I guess that also databases with NO encrypted
tables are affected by this. So: are you saying that I have to recreate
everything in order to encrypt a single table with a custom password? Or
am I mistaken?

What I need is this:

1. Install EDBManager on a client's machine in order to provide remote
support.
2. Encrypt only tables of one database.
3. Preventing that the client (or someone else) can open the encrypted
table by using EDBMAnager.

Thanks Uli.

Uli,

<< Hmmm. Not that easy. I guess that also databases with NO encrypted tables
are affected by this. So: are you saying that I have to recreate everything
in order to encrypt a single table with a custom password? Or am I mistaken?
>>

No, that is correct.  Remember, encryption in EDB is not like DBISAM where
it is somewhat of a substitute for user security.  If you want to restrict
table access, then use the user security.  If you need on-disk encryption of
data that prevents low-level inspection and editing, then you would use the
encryption.  However, the encryption requires that you plan ahead in terms
of what password you wish to use.  It is not something that is easily added
on after an application is already in the field.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> No, that is correct.  Remember, encryption in EDB is not like DBISAM where
> it is somewhat of a substitute for user security.  If you want to restrict
> table access, then use the user security.  If you need on-disk encryption of
> data that prevents low-level inspection and editing, then you would use the
> encryption.  However, the encryption requires that you plan ahead in terms
> of what password you wish to use.  It is not something that is easily added
> on after an application is already in the field.

OK, I now understand how it works. Thanks for clearifying that.

Uli