| |||||||||||
Heise reports from SCO ForumHeise reports from SCO ForumPosted Aug 19, 2003 14:43 UTC (Tue) by mk270 (guest, #4485)Parent article: Heise reports from SCO Forum Bizarrely, there is a note in the SysV screenshot where half the comment is transliterated into Greek - a one-for-one substitution of Roman letters for Greek ones yields perfect English text (relating to the renaming of the malloc() function and its friends). Probably just a font error.
(Log in to post comments)
Heise reports from SCO Forum Posted Aug 19, 2003 14:53 UTC (Tue) by BrucePerens (subscriber, #2510) [Link] Are you sure that's not delibrate obfuscation, by someone who isn't very technical in nature?Would someone please type the entire Greek paragraph in and give us a font mapping? Something that demonstrates how the font is mapped back, so that there is a trace from the SCO slide to real code, would be useful. I could really use this for a news editorial, and have no idea how to type in Latin. Bruce
Heise reports from SCO Forum Posted Aug 19, 2003 15:00 UTC (Tue) by laurent (guest, #7539) [Link] From LinuxToday... (credit Fred Flintstone)--- snip ---- "As part of the server evolution towards modular naming, Does this mean something to someone? Why bother writing it with greek I hope I'm not infringing on any copyright by copying this here :-)
Heise reports from SCO Forum Posted Aug 19, 2003 15:02 UTC (Tue) by forthy (guest, #1525) [Link] Ok, here it is in ASCII/latin1:"As part of the kernel evolution towards modular naming, the functions malloc and mfree are being renamed to rmalloc and rmfree. Compatibility will be maintained by the following assembler code: (also see mfree/rmfree below)"
Heise reports from SCO Forum Posted Aug 19, 2003 15:09 UTC (Tue) by rgmoore (subscriber, #75) [Link] Would someone please type the entire Greek paragraph in Sure. It looks as though they just switched the code in question into the standard "Symbol" font: *As part of the kernel evolution toward modular naming, the
Heise reports from SCO Forum Posted Aug 19, 2003 15:13 UTC (Tue) by allesfresser (subscriber, #216) [Link] All they did is to change the font to Symbol. (Why? I have no idea...if they were trying to keep something secret, did they think no one could read those funny foreign letters...?) Or maybe now they'll sue all of us who read and transliterated them under the DMCA for encryption-breaking...
Heise reports from SCO Forum Posted Aug 19, 2003 15:25 UTC (Tue) by rknop (guest, #66) [Link] That's not a joke.Skylarov was jailed for breaking encryption of similar security, under the DMCA. Those of you who changed the Symbol font back are in fact now federal criminals under USA law. You may wish to flee this free country now. -Rob
Heise reports from SCO Forum Posted Aug 19, 2003 15:59 UTC (Tue) by allesfresser (subscriber, #216) [Link] I guess I've got an illegal decryption device embedded in my head then... I just read the text as it was. (Thanks to whoever made the Symbol font for making the transliteration pretty easy!) How am I supposed to keep from violating the DMCA with such an embedded technology...? No, don't answer that. :-)
Heise reports from SCO Forum Posted Aug 19, 2003 16:35 UTC (Tue) by rknop (guest, #66) [Link] By trafficing in your head, you are a federal criminal.The only way to be safe is to cut it off and destroy it before the feds look at you. (And, yes, the DMCA really is that silly.) -Rob
Heise reports from SCO Forum Posted Aug 19, 2003 19:24 UTC (Tue) by tjc (guest, #137) [Link] I guess I've got an illegal decryption device embedded in my head then...I've got a parser in my head, and I'm getting a syntax error on line 2 of the second slide.
Heise reports from SCO Forum Posted Aug 19, 2003 16:08 UTC (Tue) by gups (guest, #14053) [Link] Hahahaha...That's funny.
Heise reports from SCO Forum Posted Aug 19, 2003 16:16 UTC (Tue) by shadowman99 (guest, #14165) [Link] Actually I would think SCO would be in trouble with the DMCA before anyone for violating copywrite law by changing the text as originally written. They have moddified the character set without permission of the author.By changing code in an effort to obfuscate they have done the very thing they accuse our community of. Bonk Bonk on the head!
Heise reports from SCO Forum Posted Aug 19, 2003 18:14 UTC (Tue) by mmarq (guest, #2332) [Link] So besides a Diversion, all this show could be a trap to !!!...With the "criminal" minds that are feading SCO more than clue cards, its no wonder!... What is not good, is that they can predict Linux/OSS movements... I belive a "REALLY BIG PUSH" to LSB to completly cover the Desktop, would suprise and scare them to dead! If all this sound to you as nosense, than you better think again, because you are confused about how "fox smart" business minds work.
Heise reports from SCO Forum Posted Aug 19, 2003 18:44 UTC (Tue) by dbhost (guest, #3461) [Link] to repeat a quote I have heard attributed to Krusty The Clown from The Simpsons while in Mexico."Everything's legal in Mexico. It's the American way!" If I have misquoted, or given credit to the wrong mouth that uttered that wisdom please correct me...
Heise reports from SCO Forum Posted Aug 21, 2003 7:19 UTC (Thu) by bajw (subscriber, #11712) [Link] I did a Google on the phrase, and the results showed that the phrase was"Hell, everything's legal in Mexico. It's the American Way." Google also indicated that it was said by Uncle Jimbo of Southpark.
Heise reports from SCO Forum Posted Aug 19, 2003 14:56 UTC (Tue) by rgmoore (subscriber, #75) [Link] Probably just a font error. Probably not. My guess is that switch to a Greek font was a deliberate, if lame, attempt to obscure the code. If the code in question was just flashed up on the screen for 15 seconds, you probably wouldn't have had time to figure out what that obscured section meant. I know it took me longer than that to read it. They probably weren't expecting anyone to take a picture of the screen for later perusal; otherwise they wouldn't have chosen code that (as some of the other posters here have pointed out) is easily identified in its origin not to be proprietary to SCO.
Heise reports from SCO Forum Posted Aug 19, 2003 15:26 UTC (Tue) by rknop (guest, #66) [Link] ...unless they don't *have* any copied code which isn't easily identified in its origin as not to be proprietary to SCO....-Rob
Heise reports from SCO Forum Posted Aug 19, 2003 14:56 UTC (Tue) by forthy (guest, #1525) [Link] According to the Heise article, SCO made portions of their own code (which is not identicalto Linux sources) "unreadable". That probably refers to the obfuscated text, which is IMHO quite readable (no, that's not greek to me ;-). Well, they should have tried harder. Elfish or Klingon at least. And they should also have tried harder than to dig out ancient Unix version 5 code they themselves (as Caldera) put under BSD license a few years ago. Furthermore: Dear SGI, kmalloc() should be used to allocated kernel memory, no need to brew something yourself.
Heise reports from SCO Forum Posted Aug 19, 2003 15:02 UTC (Tue) by dizzl (subscriber, #5521) [Link] Indeed. It reads:* As part of the kernel evolution towards modular naming, the * functions malloc and mfree are being renamed to rmalloc and rmfree. * Compatibility will be maintained by the following assembler code: * (also see mfree/rmfree below) * / Maybe that helps in locating the textbook...
|
|||||||||||
