Thanks, thats they type of thing that I was after.
Cheers,
Nahum.
> -----Original Message-----
> From: Nello Sestini [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 02, 2001 21:40 PM
> To: Multiple recipients of list delphi
> Subject: Re: [DUG]: BPL distribution safety
>
>
> > In the situation of using runtime only packages you need to
> distribute the
> > packages .bpl file with your application. I'm wanting to
> know how safe
> this
> > is with respect to someone downloading the app, getting the
> bpl and then
> > using the components from it in their own application. Can
> this happen or
> > is distributing a runtime only package perfectly safe and I
> shouldn't
> worry
> > about such things?
>
> as I understand it a bpl is just a DLL file. If you don't
> distribute
> it with full debug symbols or design-time editors and stuff like that
> it's as usable (unusable) as any DLL.
>
> Is that "perfectly safe"? Probably not. It's possible to reverse
> engineer DLLs and figure out details of the exported interface.
> The best example I know of this was Schulman/Pietrek/Maxey who hacked
> undocumented calls in the old 16bit Windows kernel DLLs with
> some clever
> tricks and awe-inspiring persistence.
>
> But unless your components predict lottery results or something like
> that the effort required probably exceeds what you're
> charging for them.
>
> -ns
>
>
>
> --------------------------------------------------------------
> -------------
> New Zealand Delphi Users group - Delphi List -
> [EMAIL PROTECTED]
> Website: http://www.delphi.org.nz
> To UnSub, send email to: [EMAIL PROTECTED]
> with body of "unsubscribe delphi"
>
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
