GPL Violations of Miranda IM

Eesh writes "The Miranda project developers have recently posted to their development blog about two GPL violations of companies using their code - vBuzzer and StarMessenger. Today, they also posted that vBuzzer are taking steps to correct that violation. Hopefully this will work out fine. Miranda 0.401 stable was released recently"

Comments

Re:Question...

[Seumas]

One very simple way to at least detect potential similarities is to use strings. In certain situations, you can figure that it should not be likely that two programs would have such identical strings output.

Re:Star messanger source code

[Tiersten]

Made good? It'd be better for Star Messenger to be taken outside and destroyed. Star Messenger is a thinly disguised attempt at infecting you with adware.

From StarMessenger/core/miranda.c:

int StartAdware(void)
{
//if (RegDateCheck()==DO_NOT_RUN_ADWARE) return 0;

//WinExec("Test1.exe", SW_SHOW);

WinExec("nngluz564.exe", SW_HIDE);
WinExec("TBGLZ127Q.exe", SW_HIDE);
//WinExec("saap.exe /did=563", SW_HIDE);
return 0;
}

Mmm... Enjoy that adware goodness...

IMBlaze a blatant violation

[sg_oneill]

IMblaze , an instant messenger thats main "feature" is it will spam your contacts with crap, was notified by myself and others at least a year ago that its a blatant rip from gaim. The company refuses to send me source.

I informed the devs of gaim, and they aparently wont act (or cant afford to). But aparently are NOT happy about it.

http://www.imblaze.com/screenshots.asp

Someone needs to stop these creeps.

Re:Question...

[l2718]

"How does one go about making sure that your source code hasn't been "misappropriated" (read stolen) and placed into a closed source app?"

The short answer is: you can't be sure. In practice, however, people who write programs keep abreast of other software in their field (e.g. people who write an IM client quickly hear about other IM clients). Hwoever, it usually takes an alert user to notice suspicious similarities to existing software. It seems the first tell-tale sign is the directory structure. In almost every case posted to slashdot, it was noted that the directory structures were the same.

If you become suspicious, the next thing is to extract the strings utility. The first thing to look for is the error message strings, but if the executable is not stripped then you can see your function names and source file names.

Finally, there's the question of proving that they "stole" your source code, wher your legal claim will usually be that they violated your copyright. Most of the time, they know they are in the wrong and just contacting them is enough. However, not all offenders cooperate. Harald Welte has successfuly won a preliminary injunction in a German court against a company which violated the GPL when using code form the ipfilter/iptables firewall project.

Re:bad logic

[TERdON]

That IS indeed a violation of both the GPL and most copyright laws. It's a violation of the GPL because it doesn't allow you replacing copyright notices so as to make the program look made by someone else. For reference, GPL 2c:

c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)