Hidden license information
There's been discussion and speculation lately in the forum regarding lookout beeing aquired by microsoft as a result of the original developer beeing cought of using pirated development tools. Big IT also tells tales about how his company aquired assets of others in similar cases.
That explanation is complete crap. Microsoft does not buy companies by catching them using tools without licences.
I assumed it was a troll/joke. But I'm sure I have the advantage of being mostly detached from the Microsoft dev world.
Tayssir John Gabbour
I really doubt Microsoft's lawyers advised them to engage in criminal racketeering, just to get the assets of some little company.
Why would it be criminal to include such information (license key) in, for example, a executable?
After reading "I, Cringely" articles on Microsoft and their competitive strategies, I tend to side with the belief that they will go to any lengths to get rid of competition.
I, Cringely, would know, wouldn't he.
Sometimes there is info about licensee in generated files whether they be executables or spreadsheet documents. More commonly, there is global user and machine ID information embedded in executables and documents. Even if the person has not registered and thinks themselves anonymous, they are likely to have at some point used their machine to generate a document or executable that includes identifying information. These facts are used by the fbi and others when tracking down suspects. But it can also be used, to locate and people companies that are using unlicensed software. Usually its not worth going after them. But if they have desirable assets, then it is worth going after them. Racketeering has nothing to do with this: it is a long established legal tactic that if you are going to bother going after someone its best to choose someone with assets.
"More commonly, there is global user and machine ID information embedded in executables and documents"
It's not like this is even a big secret - it was even in plain text for a while and readily viewable. But you believe what you like, Mr. Ononymous.
I guess as proof, why don't you download any one of the numerous programs that offer to scrub this information and review the documentation.
How about I just compile on two different computers with two different licenses and see that the exe's are exactly identical?
>More commonly, there is global user and machine ID information embedded in executables and documents.
"The algorithm for creating GUID/UUIDs includes the MAC address off your ethernet card. "
The random # is generated once and after that your id s always the same. So... the fact that its random and not tied to your networking card is not relevant in the least.
Fog Creek Home