1. shroud
Is it possible to shroud some includes but not the main program? I'm trying
to hide some important stuff (to protect the software from theft) but still
be able to debug the program when it crashes so it will produce something
readable that is useful.
2. Re: shroud
George Walters wrote:
> Is it possible to shroud some includes but not the main program?
Yes, when you use Eu 2.4 (or earlier) to shroud the includes.
No, when you use Eu 2.5 for shrouding.
But you can run the main program also with Eu 2.5, even when it
includes files shrouded by Eu 2.4 (or earlier).
> I'm trying
> to hide some important stuff (to protect the software from theft) but still
> be able to debug the program when it crashes so it will produce something
> readable that is useful.
Regards,
Juergen
--
The nice thing about standards is that there are so many to choose from.
3. Re: shroud
George:
If you shroud a include file that a customer is using
be sure to make READ-ONLY because if a user loads it
into some editors; the editor can add or change some bytes
corrupting the file; making the file unuseable.
My files in archive:
w32engin.ew mixedlib.e eu_engin.e win32eru.exw
Can be downloaded here:
http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan
4. Re: shroud
George Walters wrote:
> Is it possible to shroud some includes but not the main program? I'm trying
> to hide some important stuff (to protect the software from theft) but still
> be able to debug the program when it crashes so it will produce something
> readable that is useful.
Using the 2.5 binder (which I think you have - but remember to
download it again to get the official release) you can:
bindw -full_debug myprog.exw
This will give you an encrypted .exe that will produce a full,
readable ex.err file in the event of a crash, just like you'd normally
get from the interpreter. The .exe will not contain any of your
source statements, not even in encrypted form.
It's done with line number tables and other magic. 
Your main file will also be hidden.
By default, without the "-full_debug" option, you'll get
a readable, but abbreviated version of ex.err, without variable
names, and with only rough line number info.
Try it. It's much better than with the 2.4 binder.
Of course you can't trace a bound file,
if that's what you meant by "debug".
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
5. Re: shroud
George Walters wrote:
> Is it possible to shroud some includes but not the main program? I'm trying
> to hide some important stuff (to protect the software from theft) but still
> be able to debug the program when it crashes so it will produce something
> readable that is useful.
Another thing you can do in 2.5, is create a crash routine.
See crash_routine(). When any Euphoria-detected problem
occurs, your routine will get control, and it could
dump selected variable values to a file, possibly encrypting them
in some way. Your user could send you this file, or your crash routine
might e-mail the data, or the whole ex.err, directly to you.
That's what I do with some of my CGI programs.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
6. Re: shroud
- Posted by George Walters <gwalters at sc.rr.com>
Jul 28, 2005
-
Last edited Jul 29, 2005
thanks all who responded....
