[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Enigma-devel] Fw: Oxyd 2000
From: |
Tacvek |
Subject: |
Re: [Enigma-devel] Fw: Oxyd 2000 |
Date: |
Fri, 15 Oct 2004 17:53:25 -0400 |
[Daniel, for the repeated message, OE is a horrible mail agent]
Probably using a hex-editor. The executables differ in only a few
bytes. I'm not even sure the GPL forbids a modification like this, the
license mostly talks about source code, which is really not a great
help. And because enigma.exe was compressed with upx, modifying a few
bytes garbled a large chunk of the credits screen :-)
LOL. I always check for compression on software before i go to hex edit it.
(Actually I usually only resource-edit software.)
As for the GPL binary modifications don't work well with the licence because
the source for the changed version of the program would have to be
distributed, but in such a case there would not be a source code change, and
even a binary patch would not be sufficent because it would be nearly
impossible to get a compiler to spit out an executable identical to the
original.
Regardless, i suspect a hex edit would prevent upx from being able to unpack
the exe using the command line utility, and if that is the case he is in
violation of the UPX-licence.
No, at least the most recent changes are not available via CVS.
According to the savanah main page the system is now back to normal. So it
may be possible to continue a more active devlopment... You should check to
see if all the savannah feastures now work more or less like they did before
the attack.
I think so, yes.
Ok. then when i recover my computer I promise to test it, find any other
bugs that prevent a basic './autogen.sh && ./configure && make' on cygwin.
If all such problems are fixed I will be ready to finish the guide.