Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 11 to 15 of 15 total |
Using ElevateDBManager with custom database server |
Thu, Apr 12 2007 5:16 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>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 ? Essentially yes. Treat it almost as a logon screen. My belief is that EDB Manager is a developer tool not an end user one and since the defaults are public I'd store them in an .ini file or somesuch in plain text. If someone then changes those using a text editor they should know what they are doing. I wouldn't send EDB Manager to an end user and my intention is that apps delivered will carry custom coding aka licence keys for the necessary bits for the engine. Its not a massively secure approach for EDB Manager but probably as good as the one currently used and more flexible. Roy Lambert |
Thu, Apr 12 2007 3:52 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Stuart,
<< 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. >> The signature is stored as an MD5 hash, so it would be very difficult to get the signature text from the signature. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Apr 12 2007 3:54 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< My belief is that EDB Manager is a developer tool not an end user one and since the defaults are public I'd store them in an .ini file or somesuch in plain text. If someone then changes those using a text editor they should know what they are doing. >> Unfortunately, end users *do* use our utilities for working with databases. Frankly, there's nothing we can do to stop them, other than insist that our customers keep quiet about mentioning us or the product names anywhere. I'll see what I can do, although it's not particularly high on the list right now. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Apr 13 2007 5:09 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>I'll see what I can do, although it's not particularly high on the list >right now. I really don't understand why not <vbg> Roy Lambert |
Sat, Apr 14 2007 3:27 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I really don't understand why not <vbg> >> , let me count the ways....... -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
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 |