Thank Peter.

I will visit the site u mentioned for more info.

cm

--- In ib-support@yahoogroups.com, <peter@c...> wrote:
> Hi cm
>
> I'm surprised you need to hard code the key in your client, I use a
voucher distribution system for my code.
>
> There is lots of software around now to add encryption and control
over application distribution / authorisation.
>
>
> Have a look at the excellent Turbopower products like lockboxnow
public domain on sourceforge.
> try www.turbopower.com to look at the products available then do a
search on turbopower at sourceforge.
>
> http://sourceforge.net/search/ using turbopower as the search key.
>
>
> I myself have also used asprotect and for my apps now I use TSM's
SLock PK with their server option
>
> http://www.crypto-central.com/
>
> The theory on this site of how SlockPK works is well worth reading.
>
> Rgds
>
> Peter
> Cyionics
>
>
> ----- Original Message -----
> From: hee_cm18
> To: ib-support@yahoogroups.com
> Sent: Thursday, May 29, 2003 4:14 AM
> Subject: [ib-support] Delphi app connect to only one fb db
>
>
> Hi All,
>
> I am working on a Delphi application with Firebird. It will be
> distributed to several clients. In my client (Delphi), I have
> hardcoded a key and have that key in an application-system table.
> Each client will have different key value. Everytime user log-in,
> this key will be compare to prevent app connects to other
client's fb
> db.
>
> This is working fine for normal user. Even if they have other
> client's db, they can't connect using the app because key mis-
match.
> But for "super user", they can twist it by updating other's
client
> key to its own key using, for example, isql.
>
> What I want to do here is: The application can only connect to
its
> own db. It cannot use the application to browse data on other
> client's db.
>
> TIA.
>
> regards,
> cm
>
>
> Yahoo! Groups Sponsor
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
>
>
> [Non-text portions of this message have been removed]