If I understanded it correctly, the client- and server-engine username/passwords and
signature corresponds, as well as the session username/password and the database users.

If I set a custom username/password and signature for the engines, how am I able to
connect to my database via ElevateDB Manager ? I could only find username/database
settings for the session in there.

Cheers,

Heiko

Heiko,

<< If I set a custom username/password and signature for the engines, how am
I able to connect to my database via ElevateDB Manager ? I could only find
username/database settings for the session in there. >>

You'll have to modify the EDB Manager source code in order to use it with
custom signatures, etc. for your tables.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim, will do so.

Would be nice if at some time the username/password/signature can be edited in the standard ElevateDB Manager.

Heiko,

<< Would be nice if at some time the username/password/signature can be
edited in the standard ElevateDB Manager. >>

The issue is secure storage of such passwords/signatures so that they're not
visible to the end user.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


What about a simple front screen with all the details on it. A simple click and you're through to the select session etc or you can enter the details you want. There should be no problem with displaying the defaults since they're public anyway, at least they are if unlike Dave Harrison you know where to look

Roy Lambert

Tim


Thinking about it a front screen would also solve my other moan about the config path

Roy Lambert

Roy,

<< What about a simple front screen with all the details on it. A simple
click and you're through to the select session etc or you can enter the
details you want. There should be no problem with displaying the defaults
since they're public anyway, at least they are if unlike Dave Harrison you
know where to look >>

The defaults aren't the issue - the issue is someone who isn't using the
defaults not wanting just anyone being able to see their
signature/encryption password.   Or are you suggesting that we constantly
prompt for this information when the EDB Manager starts up ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Why not make it saveable by option...on the developer machine you can save your different
profiles (need not to be encrypted, what for ?)...and if you want to distribute EDBMan,
it's your own goofiness if you save the password/signature.

Heiko,

>
> Why not make it saveable by option...on the developer machine you can save your different
> profiles (need not to be encrypted, what for ?)...and if you want to distribute EDBMan,
> it's your own goofiness if you save the password/signature.
>

You could just change the EDBMan source to do this yourself.  

The only way to really protect your tables would be to use encryption, otherwise the data
is still plain text and can be extracted from the DAT files.
Your custom signature is stored in the table DAT file (i think) and could be extracted
using a hex editor.

Cheers, Stu

Stuart,

>>You could just change the EDBMan source to do this yourself.  

I _could_ change it this way for myself (and will do, if Tim decides not to implement it)
but that's not the point...if this feature wasn't something I think to be useful to other
EDB users, I wouldn't have mentioned it.

>>The only way to really protect your tables would be to use encryption, otherwise the
data is still plain text and can be extracted from the DAT files.

I was not talking about table or database encryption, but about encrypting stored EDB
Manager Connection Profiles, containing encryption passwords/signatures for different
projects. This is no security risk, unless you distribute them.

Cheers,

Heiko