Debug Info ON?

[Tom Boon]

It appears that even if I turn off debug info EurekaLog (EL) turns it on
again.

Is this true and required? If so then does this not make is much much easier
to get into the code by some hacker?

thanks

Tom

[admin]

Tom Boon wrote:
> It appears that even if I turn off debug info EurekaLog (EL) turns it on
> again.
>
> Is this true and required?

Yes it is, because EurekaLog use those debug information to create its
proprietary compressed and encrypted (with key length = 128bit) debug data.

> If so then does this not make is much much easier
> to get into the code by some hacker?

No because the "Debug Info" option add the Debugger information only in
the .DCU files not in the final compiled files, so not any Borland Debug
Information is delivered with your final compiled files.

Only the EurekaLog debug information are delivered with your compiled
file, but those Info are compressed and encrypted. If you want you can
change the encryption password via "Project/EurekaLog
Options.../Advanced/Call-Stack Options/Encryption Password" option.

This password not will be stored in the final compiled file, so the
returned call-stack will included undecipherable information
(decipherable only using the EurekaLog Viewer software and inserting the
match password).

So not any EurekaLog debug information is usable by some hacker, and not
any Borland Debug Info is delivered with your final compiled file! :)

I hope to have answered to your question, otherwise don't hesitate to
recontact to me, ok?

>
> thanks
>
> Tom
>
>


--
Best regards...

Fabio Dell'Aria.