Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 15 total |
Using ElevateDBManager with custom database server |
Mon, Apr 9 2007 3:15 PM | Permanent Link |
Heiko Knuettel | 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 |
Mon, Apr 9 2007 8:53 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | 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 |
Tue, Apr 10 2007 3:33 AM | Permanent Link |
Heiko Knuettel | Thanks Tim, will do so.
Would be nice if at some time the username/password/signature can be edited in the standard ElevateDB Manager. |
Tue, Apr 10 2007 8:54 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | 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 |
Wed, Apr 11 2007 4:47 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | 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 |
Wed, Apr 11 2007 6:36 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Thinking about it a front screen would also solve my other moan about the config path Roy Lambert |
Wed, Apr 11 2007 3:26 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | 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 |
Wed, Apr 11 2007 6:47 PM | Permanent Link |
Heiko Knuettel | 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. |
Wed, Apr 11 2007 7:39 PM | Permanent Link |
Stuart Kelly | 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 |
Wed, Apr 11 2007 8:24 PM | Permanent Link |
Heiko Knuettel | 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 |
Page 1 of 2 | Next Page » | |
Jump to Page: 1 2 |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |