[...] You could call the unpacking stub part of what is added due to the compilation process. Or you could open the sources of the (usually very short) unpacking stub. In either case you do not need to open the sources of the executable packer itself.
Joergen wrote that he'd gladly open the stub source code, HAD HE ONE (the stub gets CONSTRUCTED INDIVIDUALLY for each executable!)
And I miss a statement about "humane" use.
Indeed, it'd be good to add a sentence banning military use, and I'd prefer a shorter license too.
Lucho
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
