<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_11_23_1837238</id>
	<title>English Shell Code Could Make Security Harder</title>
	<author>ScuttleMonkey</author>
	<datestamp>1258983180000</datestamp>
	<htmltext>An anonymous reader writes to tell us that finding malicious code might have just become a little harder.  Last week at the ACM Conference on Computer and Communications Security, security researchers Joshua Mason, Sam Small, Fabian Monrose, and Greg MacManus presented a method they developed to <a href="http://www.cs.jhu.edu/~sam/ccs243-mason.pdf">generate English shell code</a> [PDF].  Using content from Wikipedia and other public works to train their engine, they convert arbitrary x86 shell code into sentences that read like spam, but are natively executable.  <i>"In this paper we revisit the assumption that shell code need be fundamentally different in structure than non-executable data. Specifically, we elucidate how one can use natural language generation techniques to produce shell code that is superficially similar to English prose. We argue that this new development poses significant challenges for in-line payload-based inspection (and emulation) as a defensive measure, and also highlights the need for designing more efficient techniques for preventing shell code injection attacks altogether."</i></htmltext>
<tokenext>An anonymous reader writes to tell us that finding malicious code might have just become a little harder .
Last week at the ACM Conference on Computer and Communications Security , security researchers Joshua Mason , Sam Small , Fabian Monrose , and Greg MacManus presented a method they developed to generate English shell code [ PDF ] .
Using content from Wikipedia and other public works to train their engine , they convert arbitrary x86 shell code into sentences that read like spam , but are natively executable .
" In this paper we revisit the assumption that shell code need be fundamentally different in structure than non-executable data .
Specifically , we elucidate how one can use natural language generation techniques to produce shell code that is superficially similar to English prose .
We argue that this new development poses significant challenges for in-line payload-based inspection ( and emulation ) as a defensive measure , and also highlights the need for designing more efficient techniques for preventing shell code injection attacks altogether .
"</tokentext>
<sentencetext>An anonymous reader writes to tell us that finding malicious code might have just become a little harder.
Last week at the ACM Conference on Computer and Communications Security, security researchers Joshua Mason, Sam Small, Fabian Monrose, and Greg MacManus presented a method they developed to generate English shell code [PDF].
Using content from Wikipedia and other public works to train their engine, they convert arbitrary x86 shell code into sentences that read like spam, but are natively executable.
"In this paper we revisit the assumption that shell code need be fundamentally different in structure than non-executable data.
Specifically, we elucidate how one can use natural language generation techniques to produce shell code that is superficially similar to English prose.
We argue that this new development poses significant challenges for in-line payload-based inspection (and emulation) as a defensive measure, and also highlights the need for designing more efficient techniques for preventing shell code injection attacks altogether.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258</id>
	<title>Confused</title>
	<author>Anonymous</author>
	<datestamp>1258987680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Does TFA talk about <b>shell</b> code or <b>assembler</b> code?</p></htmltext>
<tokenext>Does TFA talk about shell code or assembler code ?</tokentext>
<sentencetext>Does TFA talk about shell code or assembler code?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209598</id>
	<title>Re:OMG!</title>
	<author>Anonymous</author>
	<datestamp>1258990920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Shades of Neal Stephenson's <a href="http://en.wikipedia.org/wiki/Snow\_Crash" title="wikipedia.org" rel="nofollow">&quot;Snow Crash&quot;</a> [wikipedia.org], in which the language of ancient Sumeria was not merely a spoken language, but a sort of programming (of the human brain) language as well, which made it possible to create a "virus" that could spread just by seeing a certain bit pattern or hearing a particular phrase.</p></htmltext>
<tokenext>Shades of Neal Stephenson 's " Snow Crash " [ wikipedia.org ] , in which the language of ancient Sumeria was not merely a spoken language , but a sort of programming ( of the human brain ) language as well , which made it possible to create a " virus " that could spread just by seeing a certain bit pattern or hearing a particular phrase .</tokentext>
<sentencetext>Shades of Neal Stephenson's "Snow Crash" [wikipedia.org], in which the language of ancient Sumeria was not merely a spoken language, but a sort of programming (of the human brain) language as well, which made it possible to create a "virus" that could spread just by seeing a certain bit pattern or hearing a particular phrase.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210864</id>
	<title>Re:Linux version</title>
	<author>naturaverl</author>
	<datestamp>1259094900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext> Did you kids mean<p>
rm -rf /</p></htmltext>
<tokenext>Did you kids mean rm -rf /</tokentext>
<sentencetext> Did you kids mean
rm -rf /</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210158</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209270</id>
	<title>Re:The syntax should not matter..</title>
	<author>Anonymous</author>
	<datestamp>1258987740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Indeed, colour and shape should be irrevelant to the toxicity of our shells!</p><p>Btw, I, for one, welcome our new incisive literary overlords!</p></htmltext>
<tokenext>Indeed , colour and shape should be irrevelant to the toxicity of our shells ! Btw , I , for one , welcome our new incisive literary overlords !</tokentext>
<sentencetext>Indeed, colour and shape should be irrevelant to the toxicity of our shells!Btw, I, for one, welcome our new incisive literary overlords!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209208</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210654</id>
	<title>Re:Antelope museum</title>
	<author>Anonymous</author>
	<datestamp>1259005080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><blockquote><div><p>You're screwed now, x86 suckas!</p></div></blockquote><p>Okay, that's a joke but this screams self justifying for choosing something less common and more difficult to work with, what is it? SPARC? PPC?</p><p>I would like to point out that every CPU architecture is vulnerable to this sort of an attack, that's kind of the point with this sort of design. The obvious solution is strongly enforced memory permissions (ie. No-Execute on everything that isn't code from disk, and have the OS refuse all writes to executable files [and declaring a file to be executable] without superuser privileges).</p></div>
	</htmltext>
<tokenext>You 're screwed now , x86 suckas ! Okay , that 's a joke but this screams self justifying for choosing something less common and more difficult to work with , what is it ?
SPARC ? PPC ? I would like to point out that every CPU architecture is vulnerable to this sort of an attack , that 's kind of the point with this sort of design .
The obvious solution is strongly enforced memory permissions ( ie .
No-Execute on everything that is n't code from disk , and have the OS refuse all writes to executable files [ and declaring a file to be executable ] without superuser privileges ) .</tokentext>
<sentencetext>You're screwed now, x86 suckas!Okay, that's a joke but this screams self justifying for choosing something less common and more difficult to work with, what is it?
SPARC? PPC?I would like to point out that every CPU architecture is vulnerable to this sort of an attack, that's kind of the point with this sort of design.
The obvious solution is strongly enforced memory permissions (ie.
No-Execute on everything that isn't code from disk, and have the OS refuse all writes to executable files [and declaring a file to be executable] without superuser privileges).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210040</id>
	<title>Re:Antelope museum</title>
	<author>Anonymous</author>
	<datestamp>1258996080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The scariest thing about this comment is that the bit about the steamed cabbage is obviously true. Nobody will suspect.</p></htmltext>
<tokenext>The scariest thing about this comment is that the bit about the steamed cabbage is obviously true .
Nobody will suspect .</tokentext>
<sentencetext>The scariest thing about this comment is that the bit about the steamed cabbage is obviously true.
Nobody will suspect.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210070</id>
	<title>Re:Confused</title>
	<author>Ungrounded Lightning</author>
	<datestamp>1258996440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>TFA uses the security community's special term "(a) shellcode", which means something other than what it sounds like to ordinary programmers.</p><p>"A shellcode" is the infection head of an exploit - the thing you try to get to run on the target to make the rest of the exploit work.  It's in the machine language of the target, not a shell language.</p><p>It's called "a shellcode" because it typically (but not necessarily) tries to sucker the system into launching a shell to run the rest of the exploit.  The rest of the exploit may be in a shell language (depending on the shell to interpret it), a machine language executable, etc.  Or "the shellcode" may do something else than launch a shell.</p><p>This is one of the latter cases.  It's a chunk of self-modifying code (due to the limits of what instructions you can get out of English-looking text) that bootstraps its own internals into something that can act as an interpreter (or other executor) for the rest of the English-looking exploit code, then runs though that code and "makes it happen".</p><p>You can think of it as a binary executable program that depends on self-modification to get away with consisting only of combinations of bytes that look enough like English to fool spam filters which are trying to recognize executable code.</p><p>So it's a very goofy binary and there are no shells or shell languages involved.  Instead (if I read this right) the researchers built a very screwy assembler that takes as input an assembler source program and produces as output some VERY screwy machine code that looks like English and ends up doing the same job in a roundabout way, rather than being the direct translation of the assembler code input.</p></htmltext>
<tokenext>TFA uses the security community 's special term " ( a ) shellcode " , which means something other than what it sounds like to ordinary programmers .
" A shellcode " is the infection head of an exploit - the thing you try to get to run on the target to make the rest of the exploit work .
It 's in the machine language of the target , not a shell language.It 's called " a shellcode " because it typically ( but not necessarily ) tries to sucker the system into launching a shell to run the rest of the exploit .
The rest of the exploit may be in a shell language ( depending on the shell to interpret it ) , a machine language executable , etc .
Or " the shellcode " may do something else than launch a shell.This is one of the latter cases .
It 's a chunk of self-modifying code ( due to the limits of what instructions you can get out of English-looking text ) that bootstraps its own internals into something that can act as an interpreter ( or other executor ) for the rest of the English-looking exploit code , then runs though that code and " makes it happen " .You can think of it as a binary executable program that depends on self-modification to get away with consisting only of combinations of bytes that look enough like English to fool spam filters which are trying to recognize executable code.So it 's a very goofy binary and there are no shells or shell languages involved .
Instead ( if I read this right ) the researchers built a very screwy assembler that takes as input an assembler source program and produces as output some VERY screwy machine code that looks like English and ends up doing the same job in a roundabout way , rather than being the direct translation of the assembler code input .</tokentext>
<sentencetext>TFA uses the security community's special term "(a) shellcode", which means something other than what it sounds like to ordinary programmers.
"A shellcode" is the infection head of an exploit - the thing you try to get to run on the target to make the rest of the exploit work.
It's in the machine language of the target, not a shell language.It's called "a shellcode" because it typically (but not necessarily) tries to sucker the system into launching a shell to run the rest of the exploit.
The rest of the exploit may be in a shell language (depending on the shell to interpret it), a machine language executable, etc.
Or "the shellcode" may do something else than launch a shell.This is one of the latter cases.
It's a chunk of self-modifying code (due to the limits of what instructions you can get out of English-looking text) that bootstraps its own internals into something that can act as an interpreter (or other executor) for the rest of the English-looking exploit code, then runs though that code and "makes it happen".You can think of it as a binary executable program that depends on self-modification to get away with consisting only of combinations of bytes that look enough like English to fool spam filters which are trying to recognize executable code.So it's a very goofy binary and there are no shells or shell languages involved.
Instead (if I read this right) the researchers built a very screwy assembler that takes as input an assembler source program and produces as output some VERY screwy machine code that looks like English and ends up doing the same job in a roundabout way, rather than being the direct translation of the assembler code input.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209550</id>
	<title>Re:This is</title>
	<author>blueg3</author>
	<datestamp>1258990380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes -- in theory, could should be W xor X: writable or executable, but never both. This is then solved neatly. However, this is often not the case. It's a little bold on Von Neumann machines, where the code and data are the same, to hope that code and data can be cleanly separated reliably.</p><p>The most egregious case is interpreters, where data that's passed around is turned into executable code dynamically. Less egregious but still unsafe is dynamically-generated code, which must be both writable and executable.</p></htmltext>
<tokenext>Yes -- in theory , could should be W xor X : writable or executable , but never both .
This is then solved neatly .
However , this is often not the case .
It 's a little bold on Von Neumann machines , where the code and data are the same , to hope that code and data can be cleanly separated reliably.The most egregious case is interpreters , where data that 's passed around is turned into executable code dynamically .
Less egregious but still unsafe is dynamically-generated code , which must be both writable and executable .</tokentext>
<sentencetext>Yes -- in theory, could should be W xor X: writable or executable, but never both.
This is then solved neatly.
However, this is often not the case.
It's a little bold on Von Neumann machines, where the code and data are the same, to hope that code and data can be cleanly separated reliably.The most egregious case is interpreters, where data that's passed around is turned into executable code dynamically.
Less egregious but still unsafe is dynamically-generated code, which must be both writable and executable.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211202</id>
	<title>Re:This is</title>
	<author>RAMMS+EIN</author>
	<datestamp>1259058360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>``We'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place..''</p><p>This has been done. The problem is that popular operating systems and applications don't make use of these techniques.</p><p>Shellcode crash course: shellcode is basically code which an attacker feeds to a program, which the program then executes, even though it is not supposed to. Getting the program to execute the shellcode thus relies on exploiting a security vulnerability. The canonical scenario is exploiting a buffer overflow, where the attacker feeds data to the program that is larger than the buffer the program has allocated for it. Programs that don't check for this will happily overwrite their own memory, including the return address of the current function. Overwrite the return address so that it points into the data you fed the program and presto, you now control the machine.</p><p>This relies on two things:</p><p>1. The program actually overwriting memory outside the buffer when reading data into the buffer<br>2. The machine actually executing the data as code</p><p>1 is dependent on the function used to read the input. C provides several functions that allow buffer overflows, and allows the programmer to write his own. I wrote an essay years ago where I advocated using higher level programming languages for most development specifically to avoid these dangers, and, frankly, I'm baffled that we're still using C so much. Sure, if you program carefully enough, you can avoid the pitfalls, but Real World data shows that this isn't happening. Besides, there are other good reasons for using other languages, for example more powerful abstractions that lead to more productivity. But, for this discussion, what is relevant is that shellcode would not be such a problem if it wasn't for so many programs being written using unsafe constructs in C and C++.</p><p>2 is easily prevented on most architectures by marking data as non-executable. There are actually some efforts to do this: OpenBSD has W^X, Linux has PaX, and Windows nowadays has Data Execution Prevention. However, most Linux distributions do not include PaX, and the default setting for DEP in Windows is opt-in, which means that programs that do not explicitly request it don't get it. Besides W^X, there are other mechanisms, such as address space layout randomization. ASLR makes executing shellcode hard by making it hard to predict at which address shellcode and library functions reside. It is enabled by default on OpenBSD. On Linux, it is provided by PaX, which, most distributions don't include. On Windows, it has been enabled by default since Vista, but only in a very limited form.</p><p>As far as I am concerned, the ability of an attacker to inject shellcode into a system would be a solved problem, if only the world adopted the solutions.</p></htmltext>
<tokenext>` ` We 'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place..''This has been done .
The problem is that popular operating systems and applications do n't make use of these techniques.Shellcode crash course : shellcode is basically code which an attacker feeds to a program , which the program then executes , even though it is not supposed to .
Getting the program to execute the shellcode thus relies on exploiting a security vulnerability .
The canonical scenario is exploiting a buffer overflow , where the attacker feeds data to the program that is larger than the buffer the program has allocated for it .
Programs that do n't check for this will happily overwrite their own memory , including the return address of the current function .
Overwrite the return address so that it points into the data you fed the program and presto , you now control the machine.This relies on two things : 1 .
The program actually overwriting memory outside the buffer when reading data into the buffer2 .
The machine actually executing the data as code1 is dependent on the function used to read the input .
C provides several functions that allow buffer overflows , and allows the programmer to write his own .
I wrote an essay years ago where I advocated using higher level programming languages for most development specifically to avoid these dangers , and , frankly , I 'm baffled that we 're still using C so much .
Sure , if you program carefully enough , you can avoid the pitfalls , but Real World data shows that this is n't happening .
Besides , there are other good reasons for using other languages , for example more powerful abstractions that lead to more productivity .
But , for this discussion , what is relevant is that shellcode would not be such a problem if it was n't for so many programs being written using unsafe constructs in C and C + + .2 is easily prevented on most architectures by marking data as non-executable .
There are actually some efforts to do this : OpenBSD has W ^ X , Linux has PaX , and Windows nowadays has Data Execution Prevention .
However , most Linux distributions do not include PaX , and the default setting for DEP in Windows is opt-in , which means that programs that do not explicitly request it do n't get it .
Besides W ^ X , there are other mechanisms , such as address space layout randomization .
ASLR makes executing shellcode hard by making it hard to predict at which address shellcode and library functions reside .
It is enabled by default on OpenBSD .
On Linux , it is provided by PaX , which , most distributions do n't include .
On Windows , it has been enabled by default since Vista , but only in a very limited form.As far as I am concerned , the ability of an attacker to inject shellcode into a system would be a solved problem , if only the world adopted the solutions .</tokentext>
<sentencetext>``We'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place..''This has been done.
The problem is that popular operating systems and applications don't make use of these techniques.Shellcode crash course: shellcode is basically code which an attacker feeds to a program, which the program then executes, even though it is not supposed to.
Getting the program to execute the shellcode thus relies on exploiting a security vulnerability.
The canonical scenario is exploiting a buffer overflow, where the attacker feeds data to the program that is larger than the buffer the program has allocated for it.
Programs that don't check for this will happily overwrite their own memory, including the return address of the current function.
Overwrite the return address so that it points into the data you fed the program and presto, you now control the machine.This relies on two things:1.
The program actually overwriting memory outside the buffer when reading data into the buffer2.
The machine actually executing the data as code1 is dependent on the function used to read the input.
C provides several functions that allow buffer overflows, and allows the programmer to write his own.
I wrote an essay years ago where I advocated using higher level programming languages for most development specifically to avoid these dangers, and, frankly, I'm baffled that we're still using C so much.
Sure, if you program carefully enough, you can avoid the pitfalls, but Real World data shows that this isn't happening.
Besides, there are other good reasons for using other languages, for example more powerful abstractions that lead to more productivity.
But, for this discussion, what is relevant is that shellcode would not be such a problem if it wasn't for so many programs being written using unsafe constructs in C and C++.2 is easily prevented on most architectures by marking data as non-executable.
There are actually some efforts to do this: OpenBSD has W^X, Linux has PaX, and Windows nowadays has Data Execution Prevention.
However, most Linux distributions do not include PaX, and the default setting for DEP in Windows is opt-in, which means that programs that do not explicitly request it don't get it.
Besides W^X, there are other mechanisms, such as address space layout randomization.
ASLR makes executing shellcode hard by making it hard to predict at which address shellcode and library functions reside.
It is enabled by default on OpenBSD.
On Linux, it is provided by PaX, which, most distributions don't include.
On Windows, it has been enabled by default since Vista, but only in a very limited form.As far as I am concerned, the ability of an attacker to inject shellcode into a system would be a solved problem, if only the world adopted the solutions.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209886</id>
	<title>Re:This is</title>
	<author>nneonneo</author>
	<datestamp>1258994100000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Unfortunately, this does not fully solve the problem. Say, for instance, that you've managed to get a buffer overflow on a system, and you now have control over the stack (which is marked RW, but not X). Then, you overwrite the return address of the current function to mprotect() and stick some arguments on it which change the stack protection to RX (there are good reasons for doing this in actual practice, e.g. executable compressors like UPX, or executable thunks on the stack); this type of attack is known as a "return-to-libc" attack. If you can successfully overwrite the next lower return address as well, then you can ensure that your shellcode is executed after mprotect returns.</p><p>Even if we assume that the stack is permanently fixed at RW, this does not prevent heap spray attacks which place executable code on the heap and overwrite return addresses on the stack to point at the heap. If the heap is marked RW, then we can just repeat the same process as used above to call mprotect.</p><p>Prohibiting execution on writable segments seems sensible, but in the face of functions which can change the protection bits, it is ineffective. Further, simply restricting the use of those functions is potentially too restrictive, as in the case of some runtime environments which rely on the ability to execute dynamically generated trampoline code to implement key features (for instance, GCC may generate trampoline code to call nested functions), as you mentioned with your second paragraph.</p></htmltext>
<tokenext>Unfortunately , this does not fully solve the problem .
Say , for instance , that you 've managed to get a buffer overflow on a system , and you now have control over the stack ( which is marked RW , but not X ) .
Then , you overwrite the return address of the current function to mprotect ( ) and stick some arguments on it which change the stack protection to RX ( there are good reasons for doing this in actual practice , e.g .
executable compressors like UPX , or executable thunks on the stack ) ; this type of attack is known as a " return-to-libc " attack .
If you can successfully overwrite the next lower return address as well , then you can ensure that your shellcode is executed after mprotect returns.Even if we assume that the stack is permanently fixed at RW , this does not prevent heap spray attacks which place executable code on the heap and overwrite return addresses on the stack to point at the heap .
If the heap is marked RW , then we can just repeat the same process as used above to call mprotect.Prohibiting execution on writable segments seems sensible , but in the face of functions which can change the protection bits , it is ineffective .
Further , simply restricting the use of those functions is potentially too restrictive , as in the case of some runtime environments which rely on the ability to execute dynamically generated trampoline code to implement key features ( for instance , GCC may generate trampoline code to call nested functions ) , as you mentioned with your second paragraph .</tokentext>
<sentencetext>Unfortunately, this does not fully solve the problem.
Say, for instance, that you've managed to get a buffer overflow on a system, and you now have control over the stack (which is marked RW, but not X).
Then, you overwrite the return address of the current function to mprotect() and stick some arguments on it which change the stack protection to RX (there are good reasons for doing this in actual practice, e.g.
executable compressors like UPX, or executable thunks on the stack); this type of attack is known as a "return-to-libc" attack.
If you can successfully overwrite the next lower return address as well, then you can ensure that your shellcode is executed after mprotect returns.Even if we assume that the stack is permanently fixed at RW, this does not prevent heap spray attacks which place executable code on the heap and overwrite return addresses on the stack to point at the heap.
If the heap is marked RW, then we can just repeat the same process as used above to call mprotect.Prohibiting execution on writable segments seems sensible, but in the face of functions which can change the protection bits, it is ineffective.
Further, simply restricting the use of those functions is potentially too restrictive, as in the case of some runtime environments which rely on the ability to execute dynamically generated trampoline code to implement key features (for instance, GCC may generate trampoline code to call nested functions), as you mentioned with your second paragraph.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209550</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209676</id>
	<title>Re:This is</title>
	<author>Blakey Rat</author>
	<datestamp>1258991580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I know, I'm going to have to stop saving and trying to execute all my incoming spam messages.</p><p>Maybe I'll try executing my IMs...</p></htmltext>
<tokenext>I know , I 'm going to have to stop saving and trying to execute all my incoming spam messages.Maybe I 'll try executing my IMs.. .</tokentext>
<sentencetext>I know, I'm going to have to stop saving and trying to execute all my incoming spam messages.Maybe I'll try executing my IMs...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209706</id>
	<title>I CAN BE PLAYED ON RECORD PLAYER X</title>
	<author>Anonymous</author>
	<datestamp>1258991880000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Let the T-C wars continue!</p></htmltext>
<tokenext>Let the T-C wars continue !</tokentext>
<sentencetext>Let the T-C wars continue!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210346</id>
	<title>Re:This is</title>
	<author>Anonymous</author>
	<datestamp>1259000400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Meh, I only use Polish shell code.  Much more secure than the Swedish shell code I used to use:  </p><blockquote><div><p> <tt>Bash:$ Sudo Bork | Bork | Bork</tt></p></div> </blockquote></div>
	</htmltext>
<tokenext>Meh , I only use Polish shell code .
Much more secure than the Swedish shell code I used to use : Bash : $ Sudo Bork | Bork | Bork</tokentext>
<sentencetext>Meh, I only use Polish shell code.
Much more secure than the Swedish shell code I used to use:   Bash:$ Sudo Bork | Bork | Bork 
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209836</id>
	<title>This is sooo old</title>
	<author>Anonymous</author>
	<datestamp>1258993620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>That you could do this was shown waaaay back in letter submissions to PC Magazine back in the 80's.  This is not new AT ALL.</p></htmltext>
<tokenext>That you could do this was shown waaaay back in letter submissions to PC Magazine back in the 80 's .
This is not new AT ALL .</tokentext>
<sentencetext>That you could do this was shown waaaay back in letter submissions to PC Magazine back in the 80's.
This is not new AT ALL.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210312</id>
	<title>Re:Antelope museum</title>
	<author>slashqwerty</author>
	<datestamp>1258999920000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>For those that are curious, here is some actual exploit code from <a href="http://www.cs.jhu.edu/~sam/ccs243-mason.pdf" title="jhu.edu">the paper</a> [jhu.edu]:<blockquote><div><p> <b>There is a major </b>center of economic activity, suc<b>h as Star </b>Trek, including The Ed Sullivan <b>Show. The form</b>er Soviet Union. International organization participation Asian Development Bank, established in the United <b>States Dru</b>g Enforcement Administration, and the Palestinian territories, the International Telecommunication Union, the first m<b>a</b></p></div>
</blockquote><p>The bold characters are code.  The rest have no net effect.

<br> <br>Their strategy is to break the exploit into two pieces, a small executable decoder, and the payload.  As you might imagine, the decoder decodes the payload.  The payload is encoded in a benign-looking format which is simple enough.  Their goal was make the decoder also look like benign data.  To achieve that, their tool takes an existing decoder and automatically converts it to English-looking prose like the paragraph above.  The tool is able to convert a decoder is less than an hour on commodity hardware.</p></div>
	</htmltext>
<tokenext>For those that are curious , here is some actual exploit code from the paper [ jhu.edu ] : There is a major center of economic activity , such as Star Trek , including The Ed Sullivan Show .
The former Soviet Union .
International organization participation Asian Development Bank , established in the United States Drug Enforcement Administration , and the Palestinian territories , the International Telecommunication Union , the first ma The bold characters are code .
The rest have no net effect .
Their strategy is to break the exploit into two pieces , a small executable decoder , and the payload .
As you might imagine , the decoder decodes the payload .
The payload is encoded in a benign-looking format which is simple enough .
Their goal was make the decoder also look like benign data .
To achieve that , their tool takes an existing decoder and automatically converts it to English-looking prose like the paragraph above .
The tool is able to convert a decoder is less than an hour on commodity hardware .</tokentext>
<sentencetext>For those that are curious, here is some actual exploit code from the paper [jhu.edu]: There is a major center of economic activity, such as Star Trek, including The Ed Sullivan Show.
The former Soviet Union.
International organization participation Asian Development Bank, established in the United States Drug Enforcement Administration, and the Palestinian territories, the International Telecommunication Union, the first ma
The bold characters are code.
The rest have no net effect.
Their strategy is to break the exploit into two pieces, a small executable decoder, and the payload.
As you might imagine, the decoder decodes the payload.
The payload is encoded in a benign-looking format which is simple enough.
Their goal was make the decoder also look like benign data.
To achieve that, their tool takes an existing decoder and automatically converts it to English-looking prose like the paragraph above.
The tool is able to convert a decoder is less than an hour on commodity hardware.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210992</id>
	<title>Re:This is</title>
	<author>phantomcircuit</author>
	<datestamp>1259054400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I would seriously like to see you try to defeat both NX and -fstack-protector.</p></htmltext>
<tokenext>I would seriously like to see you try to defeat both NX and -fstack-protector .</tokentext>
<sentencetext>I would seriously like to see you try to defeat both NX and -fstack-protector.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209886</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211092</id>
	<title>Re:Antelope museum</title>
	<author>Anonymous</author>
	<datestamp>1259056440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>What?? My mother was a saint!</htmltext>
<tokenext>What ? ?
My mother was a saint !</tokentext>
<sentencetext>What??
My mother was a saint!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209204</id>
	<title>haha</title>
	<author>Anonymous</author>
	<datestamp>1258987200000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>first. n&#228;r&#229;.</p></htmltext>
<tokenext>first .
n   r   .</tokentext>
<sentencetext>first.
närå.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209948</id>
	<title>Excellent Presentation</title>
	<author>rochberg</author>
	<datestamp>1258994940000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>This talk was probably my favorite at CCS this year.  Unlike MANY researchers, the lead author of this paper was quite entertaining.  Regarding the work itself, there are a few details that the current discussion has missed.</p><p>First, I would not say that they can convert <b>arbitrary</b> shell code to English-like prose.  Rather, the only instructions that can be used are the ones that are <b>identical</b> to the ASCII encoding of the alphabet.  For instance, the ASCII encoding of the letter "r" is identical to the binary for the unconditional jmp instruction.  Granted, the authors showed that you can do a lot with this limited set of instructions, but I still wouldn't call it arbitrary.</p><p>Second, he showed several examples of the sentences created.  They make about as much sense as "Lorem ipsum dolor sit amet..."  The tight constraints on the instructions that can be encoded into ASCII make crafting decent English syntax nearly impossible.  Spam filters based on natural language processing could probably detect and flag them.</p><p>While disguising the binary as ASCII is cool, I don't see that it's all that different than other exploits.  Once a sentence containing an exploit is detected, you'll have signatures just like any other type of virus/trojan.  I highly doubt that contemporary anti-virus scanners stop working on data that looks like ASCII.  Rather, they look for tell-tale signs of particular instructions that appear in particular orders, etc.</p><p>And, as many others have pointed out, this code is only harmful if it is executed in the right context (i.e., you have a vulnerability to exploit).  Disguising the code as ASCII doesn't really make it different than any other type of zero-day attack.</p><p>This work was very sophisticated, and there's no way that script kiddies could build something like this.  I don't know that more advanced attackers would bother, because I really don't see all that much of a payoff given the amount of work that this attack requires.  It's a whole lot easier to take over a vulnerable web server and launch a XSS attack.  The incentives simply do not seem to suggest that this technique will become widespread.</p><p>So, no, I don't think the sky is falling because of this attack.  Having said that, though, this was a very cool piece of work.</p></htmltext>
<tokenext>This talk was probably my favorite at CCS this year .
Unlike MANY researchers , the lead author of this paper was quite entertaining .
Regarding the work itself , there are a few details that the current discussion has missed.First , I would not say that they can convert arbitrary shell code to English-like prose .
Rather , the only instructions that can be used are the ones that are identical to the ASCII encoding of the alphabet .
For instance , the ASCII encoding of the letter " r " is identical to the binary for the unconditional jmp instruction .
Granted , the authors showed that you can do a lot with this limited set of instructions , but I still would n't call it arbitrary.Second , he showed several examples of the sentences created .
They make about as much sense as " Lorem ipsum dolor sit amet... " The tight constraints on the instructions that can be encoded into ASCII make crafting decent English syntax nearly impossible .
Spam filters based on natural language processing could probably detect and flag them.While disguising the binary as ASCII is cool , I do n't see that it 's all that different than other exploits .
Once a sentence containing an exploit is detected , you 'll have signatures just like any other type of virus/trojan .
I highly doubt that contemporary anti-virus scanners stop working on data that looks like ASCII .
Rather , they look for tell-tale signs of particular instructions that appear in particular orders , etc.And , as many others have pointed out , this code is only harmful if it is executed in the right context ( i.e. , you have a vulnerability to exploit ) .
Disguising the code as ASCII does n't really make it different than any other type of zero-day attack.This work was very sophisticated , and there 's no way that script kiddies could build something like this .
I do n't know that more advanced attackers would bother , because I really do n't see all that much of a payoff given the amount of work that this attack requires .
It 's a whole lot easier to take over a vulnerable web server and launch a XSS attack .
The incentives simply do not seem to suggest that this technique will become widespread.So , no , I do n't think the sky is falling because of this attack .
Having said that , though , this was a very cool piece of work .</tokentext>
<sentencetext>This talk was probably my favorite at CCS this year.
Unlike MANY researchers, the lead author of this paper was quite entertaining.
Regarding the work itself, there are a few details that the current discussion has missed.First, I would not say that they can convert arbitrary shell code to English-like prose.
Rather, the only instructions that can be used are the ones that are identical to the ASCII encoding of the alphabet.
For instance, the ASCII encoding of the letter "r" is identical to the binary for the unconditional jmp instruction.
Granted, the authors showed that you can do a lot with this limited set of instructions, but I still wouldn't call it arbitrary.Second, he showed several examples of the sentences created.
They make about as much sense as "Lorem ipsum dolor sit amet..."  The tight constraints on the instructions that can be encoded into ASCII make crafting decent English syntax nearly impossible.
Spam filters based on natural language processing could probably detect and flag them.While disguising the binary as ASCII is cool, I don't see that it's all that different than other exploits.
Once a sentence containing an exploit is detected, you'll have signatures just like any other type of virus/trojan.
I highly doubt that contemporary anti-virus scanners stop working on data that looks like ASCII.
Rather, they look for tell-tale signs of particular instructions that appear in particular orders, etc.And, as many others have pointed out, this code is only harmful if it is executed in the right context (i.e., you have a vulnerability to exploit).
Disguising the code as ASCII doesn't really make it different than any other type of zero-day attack.This work was very sophisticated, and there's no way that script kiddies could build something like this.
I don't know that more advanced attackers would bother, because I really don't see all that much of a payoff given the amount of work that this attack requires.
It's a whole lot easier to take over a vulnerable web server and launch a XSS attack.
The incentives simply do not seem to suggest that this technique will become widespread.So, no, I don't think the sky is falling because of this attack.
Having said that, though, this was a very cool piece of work.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212844</id>
	<title>Re:This is</title>
	<author>Anonymous</author>
	<datestamp>1259073300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Why you talking about trimming beards? Hold on, there is a bunch of outgoing smtp traffic on machine suddenly...</p></htmltext>
<tokenext>Why you talking about trimming beards ?
Hold on , there is a bunch of outgoing smtp traffic on machine suddenly.. .</tokentext>
<sentencetext>Why you talking about trimming beards?
Hold on, there is a bunch of outgoing smtp traffic on machine suddenly...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210914</id>
	<title>The Zork Attack</title>
	<author>tjstork</author>
	<datestamp>1259096040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's research?</p><p>Wow... my system is insecure, once I have a hooptie that can convert XYZ into assembly language, and run it, on my machine.  OMFG!!</p><p>Why do that like that? Hell, we could even claim that all shell systems are vulnerable to Zork!  I could just as easily have a tiny resident thing that can translate text adventure commands to native assembly language and compromise a machine.</p><p>r0 = the mail box<br>r1 = the white house<br>r2 = flood control dam #1</p><p>leave house.  take letter from mail box.<br>it's very dark, you are likely to be eaten by a grue...  [oh no, my victim's machine has detected my zork attack!  I must do something...]<br>light torch.<br>you have been eaten by a grue! [they kicked me out of the account]</p><p>maybe I will have to have  a planetfall attack next.</p><p>we map floyd to r0</p><p>give floyd the...</p></htmltext>
<tokenext>That 's research ? Wow... my system is insecure , once I have a hooptie that can convert XYZ into assembly language , and run it , on my machine .
OMFG ! ! Why do that like that ?
Hell , we could even claim that all shell systems are vulnerable to Zork !
I could just as easily have a tiny resident thing that can translate text adventure commands to native assembly language and compromise a machine.r0 = the mail boxr1 = the white houser2 = flood control dam # 1leave house .
take letter from mail box.it 's very dark , you are likely to be eaten by a grue... [ oh no , my victim 's machine has detected my zork attack !
I must do something... ] light torch.you have been eaten by a grue !
[ they kicked me out of the account ] maybe I will have to have a planetfall attack next.we map floyd to r0give floyd the.. .</tokentext>
<sentencetext>That's research?Wow... my system is insecure, once I have a hooptie that can convert XYZ into assembly language, and run it, on my machine.
OMFG!!Why do that like that?
Hell, we could even claim that all shell systems are vulnerable to Zork!
I could just as easily have a tiny resident thing that can translate text adventure commands to native assembly language and compromise a machine.r0 = the mail boxr1 = the white houser2 = flood control dam #1leave house.
take letter from mail box.it's very dark, you are likely to be eaten by a grue...  [oh no, my victim's machine has detected my zork attack!
I must do something...]light torch.you have been eaten by a grue!
[they kicked me out of the account]maybe I will have to have  a planetfall attack next.we map floyd to r0give floyd the...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210114</id>
	<title>Re:This is</title>
	<author>zippthorne</author>
	<datestamp>1258997220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's even worse than that.  With liberal use of jumps, the hackers can edit the jumped-over text to make sentences that actually mean something, rather than simply superficially looking like English.  They could, for instance, combine a fork bomb with a screed about cheap haircuts that really aren't.</p><p>Now, if I'm reading right, on page 7 there is a diagram which seems to imply that they also have a solution to the halting problem...</p></htmltext>
<tokenext>It 's even worse than that .
With liberal use of jumps , the hackers can edit the jumped-over text to make sentences that actually mean something , rather than simply superficially looking like English .
They could , for instance , combine a fork bomb with a screed about cheap haircuts that really are n't.Now , if I 'm reading right , on page 7 there is a diagram which seems to imply that they also have a solution to the halting problem.. .</tokentext>
<sentencetext>It's even worse than that.
With liberal use of jumps, the hackers can edit the jumped-over text to make sentences that actually mean something, rather than simply superficially looking like English.
They could, for instance, combine a fork bomb with a screed about cheap haircuts that really aren't.Now, if I'm reading right, on page 7 there is a diagram which seems to imply that they also have a solution to the halting problem...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</id>
	<title>OMG!</title>
	<author>Anonymous</author>
	<datestamp>1258987980000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Now your brain can catch a virus just by reading!!!1</htmltext>
<tokenext>Now your brain can catch a virus just by reading ! !
! 1</tokentext>
<sentencetext>Now your brain can catch a virus just by reading!!
!1</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209510</id>
	<title>Re:That was rather pretty</title>
	<author>sten ben</author>
	<datestamp>1258989960000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Looks like <a href="http://www.latex-project.org/" title="latex-project.org" rel="nofollow">LaTeX</a> [latex-project.org] with a <a href="http://hci.rwth-aachen.de/chi-template" title="rwth-aachen.de" rel="nofollow">CHI</a> [rwth-aachen.de] template. But maybe that was what you were getting at? Pretty it is.</htmltext>
<tokenext>Looks like LaTeX [ latex-project.org ] with a CHI [ rwth-aachen.de ] template .
But maybe that was what you were getting at ?
Pretty it is .</tokentext>
<sentencetext>Looks like LaTeX [latex-project.org] with a CHI [rwth-aachen.de] template.
But maybe that was what you were getting at?
Pretty it is.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209324</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30215450</id>
	<title>Re: Christmas</title>
	<author>TaoPhoenix</author>
	<datestamp>1259085240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Are your last three sentences product placements or shell code? : )</p></htmltext>
<tokenext>Are your last three sentences product placements or shell code ?
: )</tokentext>
<sentencetext>Are your last three sentences product placements or shell code?
: )</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210578</id>
	<title>Shit!!</title>
	<author>Anonymous</author>
	<datestamp>1259003760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Execute this!</p><p>eNodzMENgDAMA8C2lKhBBCT23xXQ5XEf27mf3t7/BieDi8mDJ4sXW7diMFnsQ8qdwWRxbDoMJott+sPJYLL4AQqYgLI=</p></htmltext>
<tokenext>Execute this ! eNodzMENgDAMA8C2lKhBBCT23xXQ5XEf27mf3t7/BieDi8mDJ4sXW7diMFnsQ8qdwWRxbDoMJott + sPJYLL4AQqYgLI =</tokentext>
<sentencetext>Execute this!eNodzMENgDAMA8C2lKhBBCT23xXQ5XEf27mf3t7/BieDi8mDJ4sXW7diMFnsQ8qdwWRxbDoMJott+sPJYLL4AQqYgLI=</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211066</id>
	<title>This brings back memories</title>
	<author>Anonymous</author>
	<datestamp>1259055780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>When I was a kid in the 80's, me and some class mates used to do this by hand. The game was to make as much text as possible in executable code, i.e. not just filling that was jumped over. Using a language with a more flexible grammar and word order, more available words and few more characters than English propably helped a lot, but the longest program anyone wrote in 100\% runnable code/readable text was still less then 1/3 of an A4 (and quite a lot of JMPs and RETs). As I recall, that particular program particular made the hard drive sounds say "fitta" ("cunt" in Swedish).</p></htmltext>
<tokenext>When I was a kid in the 80 's , me and some class mates used to do this by hand .
The game was to make as much text as possible in executable code , i.e .
not just filling that was jumped over .
Using a language with a more flexible grammar and word order , more available words and few more characters than English propably helped a lot , but the longest program anyone wrote in 100 \ % runnable code/readable text was still less then 1/3 of an A4 ( and quite a lot of JMPs and RETs ) .
As I recall , that particular program particular made the hard drive sounds say " fitta " ( " cunt " in Swedish ) .</tokentext>
<sentencetext>When I was a kid in the 80's, me and some class mates used to do this by hand.
The game was to make as much text as possible in executable code, i.e.
not just filling that was jumped over.
Using a language with a more flexible grammar and word order, more available words and few more characters than English propably helped a lot, but the longest program anyone wrote in 100\% runnable code/readable text was still less then 1/3 of an A4 (and quite a lot of JMPs and RETs).
As I recall, that particular program particular made the hard drive sounds say "fitta" ("cunt" in Swedish).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209718</id>
	<title>Re:Confused</title>
	<author>Blakey Rat</author>
	<datestamp>1258992000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Shellembler code.</p><p>Common mistake.</p></htmltext>
<tokenext>Shellembler code.Common mistake .</tokentext>
<sentencetext>Shellembler code.Common mistake.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209232</id>
	<title>Oh great - that love letter from the IRS</title>
	<author>rcpitt</author>
	<datestamp>1258987380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>just formatted my hard disk and installed Windows 7 - how low can you get<nobr> <wbr></nobr>:(</htmltext>
<tokenext>just formatted my hard disk and installed Windows 7 - how low can you get : (</tokentext>
<sentencetext>just formatted my hard disk and installed Windows 7 - how low can you get :(</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209950</id>
	<title>You have...</title>
	<author>slimjim8094</author>
	<datestamp>1258994940000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>You have<br>a virus<br>Didn't you know?<br>You shouldn't be<br>running Windows<br>Burma Shave</p></htmltext>
<tokenext>You havea virusDid n't you know ? You should n't berunning WindowsBurma Shave</tokentext>
<sentencetext>You havea virusDidn't you know?You shouldn't berunning WindowsBurma Shave</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209776</id>
	<title>This still means there's an interpreter</title>
	<author>uuddlrlrab</author>
	<datestamp>1258992720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>...so, as the article suggests, AV's/firewalls will look for that. And if there's a library of some sort that contains the translations, mightn't the executable portion of the payload bear some similarities to an unpacker? I'd assume they'd be unpacking (probably into the same hidden portion of memory as it) some sort of lookup table/library in order to function properly, as, presumably, they wouldn't want to include the lookup values in the exe as it would increase size &amp; risk of detection.</htmltext>
<tokenext>...so , as the article suggests , AV 's/firewalls will look for that .
And if there 's a library of some sort that contains the translations , might n't the executable portion of the payload bear some similarities to an unpacker ?
I 'd assume they 'd be unpacking ( probably into the same hidden portion of memory as it ) some sort of lookup table/library in order to function properly , as , presumably , they would n't want to include the lookup values in the exe as it would increase size &amp; risk of detection .</tokentext>
<sentencetext>...so, as the article suggests, AV's/firewalls will look for that.
And if there's a library of some sort that contains the translations, mightn't the executable portion of the payload bear some similarities to an unpacker?
I'd assume they'd be unpacking (probably into the same hidden portion of memory as it) some sort of lookup table/library in order to function properly, as, presumably, they wouldn't want to include the lookup values in the exe as it would increase size &amp; risk of detection.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210078</id>
	<title>Re:In other news...Christmas gifts</title>
	<author>polymeris</author>
	<datestamp>1258996680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It really reads like spam...Tried it and seems it's decss!</p></htmltext>
<tokenext>It really reads like spam...Tried it and seems it 's decss !</tokentext>
<sentencetext>It really reads like spam...Tried it and seems it's decss!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209342</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30216142</id>
	<title>Re:OMG!</title>
	<author>Anonymous</author>
	<datestamp>1259088480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>No its an offical Mormon Jigsaw - erm, no - a German Mixup Code!</p></htmltext>
<tokenext>No its an offical Mormon Jigsaw - erm , no - a German Mixup Code !</tokentext>
<sentencetext>No its an offical Mormon Jigsaw - erm, no - a German Mixup Code!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210160</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211056</id>
	<title>Re:Excellent Presentation</title>
	<author>npcompleat</author>
	<datestamp>1259055660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm surprised that they don't seem to be aware of the EICAR test file. From Wikipedia "The EICAR test file (official name: EICAR Standard Anti-Virus Test File) is a file, developed by the European Institute for Computer Antivirus Research, to test the response of computer antivirus (AV) programs.<nobr> <wbr></nobr>... The file is simply a text file of either 68 or 70 bytes that is a legitimate executable file<nobr> <wbr></nobr>..."</p><p>The actual test file contents are "X5O!P\%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*". It's a COM file that when run will print "EICAR-STANDARD-ANTIVIRUS-TEST-FILE!"</p></htmltext>
<tokenext>I 'm surprised that they do n't seem to be aware of the EICAR test file .
From Wikipedia " The EICAR test file ( official name : EICAR Standard Anti-Virus Test File ) is a file , developed by the European Institute for Computer Antivirus Research , to test the response of computer antivirus ( AV ) programs .
... The file is simply a text file of either 68 or 70 bytes that is a legitimate executable file ... " The actual test file contents are " X5O ! P \ % @ AP [ 4 \ PZX54 ( P ^ ) 7CC ) 7 } $ EICAR-STANDARD-ANTIVIRUS-TEST-FILE ! $ H + H * " .
It 's a COM file that when run will print " EICAR-STANDARD-ANTIVIRUS-TEST-FILE !
"</tokentext>
<sentencetext>I'm surprised that they don't seem to be aware of the EICAR test file.
From Wikipedia "The EICAR test file (official name: EICAR Standard Anti-Virus Test File) is a file, developed by the European Institute for Computer Antivirus Research, to test the response of computer antivirus (AV) programs.
... The file is simply a text file of either 68 or 70 bytes that is a legitimate executable file ..."The actual test file contents are "X5O!P\%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*".
It's a COM file that when run will print "EICAR-STANDARD-ANTIVIRUS-TEST-FILE!
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209948</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211256</id>
	<title>English Shell Code...?</title>
	<author>kirill.s</author>
	<datestamp>1259059140000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>unzip; strip; touch; finger; grep; mount; fsck; more; yes; fsck; fsck; fsck; umount; sleep;</htmltext>
<tokenext>unzip ; strip ; touch ; finger ; grep ; mount ; fsck ; more ; yes ; fsck ; fsck ; fsck ; umount ; sleep ;</tokentext>
<sentencetext>unzip; strip; touch; finger; grep; mount; fsck; more; yes; fsck; fsck; fsck; umount; sleep;</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</id>
	<title>This is</title>
	<author>Anrego</author>
	<datestamp>1258987260000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p>quite terrifying<nobr> <wbr></nobr>:(</p><p>If hackers convert arbitrary x86 shell code into sentences that read like spam, but are natively executable<nobr> <wbr></nobr>.. we're all screwed<nobr> <wbr></nobr>:(</p><p>We'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place.. or come up with sophisticated AI to help filter out the shell code. Of course, as soon as we do that, hackers will develop AIs which can write convincing (and even compelling) shell code.. and THEN what the hell do we do.</p><p>Now where I live you can get a pretty decent hair cut for $17 (they even trim up the beard). You can't get anything fancy.. but a decent, professional-ish type haircut is definitely no problem.</p><p>My employer is giving us a pretty generous Christmas vacation.. really looking forward to that!!</p><p>Also this time of year is great cause CHRISTMAS is everywhere<nobr> <wbr></nobr>:D</p></htmltext>
<tokenext>quite terrifying : ( If hackers convert arbitrary x86 shell code into sentences that read like spam , but are natively executable .. we 're all screwed : ( We 'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place.. or come up with sophisticated AI to help filter out the shell code .
Of course , as soon as we do that , hackers will develop AIs which can write convincing ( and even compelling ) shell code.. and THEN what the hell do we do.Now where I live you can get a pretty decent hair cut for $ 17 ( they even trim up the beard ) .
You ca n't get anything fancy.. but a decent , professional-ish type haircut is definitely no problem.My employer is giving us a pretty generous Christmas vacation.. really looking forward to that !
! Also this time of year is great cause CHRISTMAS is everywhere : D</tokentext>
<sentencetext>quite terrifying :(If hackers convert arbitrary x86 shell code into sentences that read like spam, but are natively executable .. we're all screwed :(We'll either need to tighten up how architectures execute instructions to make it harder to execute shell code in the first place.. or come up with sophisticated AI to help filter out the shell code.
Of course, as soon as we do that, hackers will develop AIs which can write convincing (and even compelling) shell code.. and THEN what the hell do we do.Now where I live you can get a pretty decent hair cut for $17 (they even trim up the beard).
You can't get anything fancy.. but a decent, professional-ish type haircut is definitely no problem.My employer is giving us a pretty generous Christmas vacation.. really looking forward to that!
!Also this time of year is great cause CHRISTMAS is everywhere :D</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30220392</id>
	<title>Re:So what?</title>
	<author>StrongAxe</author>
	<datestamp>1259064960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This isn't about making English prose that humans are expected to read and make sense of. Rather, it's about making English prose that anti-spam and anti-virus filters won't automatically flag and delete. If somebody has a web page or an email that exploits a vulnerablity, a good anti-spam or anti-virus filter could prevent it from loading based on the payload alone, without even having to know about the vulnerability itself (While vulnerabilities constantly change, the rules governing what is valid x86 code do not). Now, however, this is no longer the case.</htmltext>
<tokenext>This is n't about making English prose that humans are expected to read and make sense of .
Rather , it 's about making English prose that anti-spam and anti-virus filters wo n't automatically flag and delete .
If somebody has a web page or an email that exploits a vulnerablity , a good anti-spam or anti-virus filter could prevent it from loading based on the payload alone , without even having to know about the vulnerability itself ( While vulnerabilities constantly change , the rules governing what is valid x86 code do not ) .
Now , however , this is no longer the case .</tokentext>
<sentencetext>This isn't about making English prose that humans are expected to read and make sense of.
Rather, it's about making English prose that anti-spam and anti-virus filters won't automatically flag and delete.
If somebody has a web page or an email that exploits a vulnerablity, a good anti-spam or anti-virus filter could prevent it from loading based on the payload alone, without even having to know about the vulnerability itself (While vulnerabilities constantly change, the rules governing what is valid x86 code do not).
Now, however, this is no longer the case.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209794</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212816</id>
	<title>Re:Linux version</title>
	<author>Anonymous</author>
	<datestamp>1259073180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>They also came up with a Linux version, which even works on non-x86 architectures, all the while looking like plain English:</p><p>"Please type the following on your command-line:</p><p>rm -rf *</p><p>Thank you."</p></div><p>And there's the really interesting version:</p><p>"Please type the following on your command-line, as root:</p><p>rm -rf<nobr> <wbr></nobr>/*</p><p>Thank you."</p></div>
	</htmltext>
<tokenext>They also came up with a Linux version , which even works on non-x86 architectures , all the while looking like plain English : " Please type the following on your command-line : rm -rf * Thank you .
" And there 's the really interesting version : " Please type the following on your command-line , as root : rm -rf / * Thank you .
"</tokentext>
<sentencetext>They also came up with a Linux version, which even works on non-x86 architectures, all the while looking like plain English:"Please type the following on your command-line:rm -rf *Thank you.
"And there's the really interesting version:"Please type the following on your command-line, as root:rm -rf /*Thank you.
"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212762</id>
	<title>Re:This is</title>
	<author>V!NCENT</author>
	<datestamp>1259072940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How about, I don't know, making sure you just can't automagically execute shellcode and make sure that there's at least nothing skippabble, and if so, return an error?</p><p>For fsck sake... If anything. This type of exploit doesn't even work on modern Ubuntu, unless you are a complete fscking tetard.</p><p>PEBKAC.</p></htmltext>
<tokenext>How about , I do n't know , making sure you just ca n't automagically execute shellcode and make sure that there 's at least nothing skippabble , and if so , return an error ? For fsck sake... If anything .
This type of exploit does n't even work on modern Ubuntu , unless you are a complete fscking tetard.PEBKAC .</tokentext>
<sentencetext>How about, I don't know, making sure you just can't automagically execute shellcode and make sure that there's at least nothing skippabble, and if so, return an error?For fsck sake... If anything.
This type of exploit doesn't even work on modern Ubuntu, unless you are a complete fscking tetard.PEBKAC.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209280</id>
	<title>Re:This is</title>
	<author>aurelianito</author>
	<datestamp>1258987800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Mode parent insightful. He is showing how this "shellcode" would look like.</htmltext>
<tokenext>Mode parent insightful .
He is showing how this " shellcode " would look like .</tokentext>
<sentencetext>Mode parent insightful.
He is showing how this "shellcode" would look like.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209688</id>
	<title>Re:Antelope museum</title>
	<author>Twide</author>
	<datestamp>1258991640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Two Words. Google Translate

Clearly I have been receiving infestation after infestation for years, now I FINALLY know what's going on here..

So much for Don't be Evil !!!!</htmltext>
<tokenext>Two Words .
Google Translate Clearly I have been receiving infestation after infestation for years , now I FINALLY know what 's going on here. . So much for Do n't be Evil ! ! !
!</tokentext>
<sentencetext>Two Words.
Google Translate

Clearly I have been receiving infestation after infestation for years, now I FINALLY know what's going on here..

So much for Don't be Evil !!!
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209324</id>
	<title>That was rather pretty</title>
	<author>jaymz2k4</author>
	<datestamp>1258988100000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I just have to point out how well that PDF looked from a purely graphic point of view... That is all. Interesting content to boot.</htmltext>
<tokenext>I just have to point out how well that PDF looked from a purely graphic point of view... That is all .
Interesting content to boot .</tokentext>
<sentencetext>I just have to point out how well that PDF looked from a purely graphic point of view... That is all.
Interesting content to boot.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209474</id>
	<title>OK this explains a lot</title>
	<author>gzipped\_tar</author>
	<datestamp>1258989660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Newsflash: It's not the elusive and mystified <a href="http://hardware.slashdot.org/comments.pl?sid=1196619&amp;cid=27553143" title="slashdot.org" rel="nofollow">http://hardware.slashdot.org/comments.pl?sid=1196619&amp;cid=27553143</a> [slashdot.org]SlashDotFS. Those gibberish spam posts here are actually designed to crash and pwn Windoze suxx0rs...</htmltext>
<tokenext>Newsflash : It 's not the elusive and mystified http : //hardware.slashdot.org/comments.pl ? sid = 1196619&amp;cid = 27553143 [ slashdot.org ] SlashDotFS .
Those gibberish spam posts here are actually designed to crash and pwn Windoze suxx0rs.. .</tokentext>
<sentencetext>Newsflash: It's not the elusive and mystified http://hardware.slashdot.org/comments.pl?sid=1196619&amp;cid=27553143 [slashdot.org]SlashDotFS.
Those gibberish spam posts here are actually designed to crash and pwn Windoze suxx0rs...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211934</id>
	<title>Re:Antelope museum</title>
	<author>wdef</author>
	<datestamp>1259066640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Now I'm going to have nightmares thinking about that elephant's sock puppet master.  Will I ever get out of the cheese log cabin?
Look, it's clear that you're influenced by the French symbolists but can we please have less terrifying poetry?</htmltext>
<tokenext>Now I 'm going to have nightmares thinking about that elephant 's sock puppet master .
Will I ever get out of the cheese log cabin ?
Look , it 's clear that you 're influenced by the French symbolists but can we please have less terrifying poetry ?</tokentext>
<sentencetext>Now I'm going to have nightmares thinking about that elephant's sock puppet master.
Will I ever get out of the cheese log cabin?
Look, it's clear that you're influenced by the French symbolists but can we please have less terrifying poetry?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210744</id>
	<title>re: zero day exploit</title>
	<author>Anonymous</author>
	<datestamp>1259093040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>#!/bin/bash<br>Roses are red; violets are blue.<br>In Soviet Russia, all our base are belong to you.</p></htmltext>
<tokenext># ! /bin/bashRoses are red ; violets are blue.In Soviet Russia , all our base are belong to you .</tokentext>
<sentencetext>#!/bin/bashRoses are red; violets are blue.In Soviet Russia, all our base are belong to you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209288</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210248</id>
	<title>How about Finnish?</title>
	<author>Anonymous</author>
	<datestamp>1258999020000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Want to improve security? Write your kernel in Finnish.</p><p>"Linuksen algoritmi oli l&#228;hes t&#228;ydellinen h&#228;nen hivelless&#228;&#228;n Marjutan pehmeit&#228; ja py&#246;reit&#228; rintoja."</p></htmltext>
<tokenext>Want to improve security ?
Write your kernel in Finnish .
" Linuksen algoritmi oli l   hes t   ydellinen h   nen hivelless     n Marjutan pehmeit   ja py   reit   rintoja .
"</tokentext>
<sentencetext>Want to improve security?
Write your kernel in Finnish.
"Linuksen algoritmi oli lähes täydellinen hänen hivellessään Marjutan pehmeitä ja pyöreitä rintoja.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213178</id>
	<title>Re:Linux version</title>
	<author>HyperQuantum</author>
	<datestamp>1259075220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Actually, the second line doesn't look like plain English to me<nobr> <wbr></nobr>:)</htmltext>
<tokenext>Actually , the second line does n't look like plain English to me : )</tokentext>
<sentencetext>Actually, the second line doesn't look like plain English to me :)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196</id>
	<title>In other news...</title>
	<author>Anonymous</author>
	<datestamp>1258987200000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>-1</modscore>
	<htmltext><p>...3 researchers develops their own x86-assembler.</p></htmltext>
<tokenext>...3 researchers develops their own x86-assembler .</tokentext>
<sentencetext>...3 researchers develops their own x86-assembler.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209972</id>
	<title>summary title</title>
	<author>yanyan</author>
	<datestamp>1258995060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"English Shell Code Could Make Security Harder"</p><p>I was disappointed to find after reading the summary and article that english shell code doesn't improve security after all. What a misleading title.</p></htmltext>
<tokenext>" English Shell Code Could Make Security Harder " I was disappointed to find after reading the summary and article that english shell code does n't improve security after all .
What a misleading title .</tokentext>
<sentencetext>"English Shell Code Could Make Security Harder"I was disappointed to find after reading the summary and article that english shell code doesn't improve security after all.
What a misleading title.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213508</id>
	<title>Re:This is</title>
	<author>Goaway</author>
	<datestamp>1259077200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This attacks one layer of security. NX provides another layer of security. The two are not related in any way except for being layers of security.</p></htmltext>
<tokenext>This attacks one layer of security .
NX provides another layer of security .
The two are not related in any way except for being layers of security .</tokentext>
<sentencetext>This attacks one layer of security.
NX provides another layer of security.
The two are not related in any way except for being layers of security.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213498</id>
	<title>Re:Why run the code?</title>
	<author>Gleapsite</author>
	<datestamp>1259077140000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Its a stenographic method. It requires some executing code (malware, software vunerability, w/e) to jump to the ASCII text and begin executing it.

Its like camouflaging the battering ram to look like the countryside.  You still need someone on the inside to lower the drawbridge.</htmltext>
<tokenext>Its a stenographic method .
It requires some executing code ( malware , software vunerability , w/e ) to jump to the ASCII text and begin executing it .
Its like camouflaging the battering ram to look like the countryside .
You still need someone on the inside to lower the drawbridge .</tokentext>
<sentencetext>Its a stenographic method.
It requires some executing code (malware, software vunerability, w/e) to jump to the ASCII text and begin executing it.
Its like camouflaging the battering ram to look like the countryside.
You still need someone on the inside to lower the drawbridge.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211508</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211278</id>
	<title>Re:OMG!</title>
	<author>damburger</author>
	<datestamp>1259059740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Its not outside the realms of possibility... you make a bit of malicious code that hides in a very meme-y bit of text, then it can as easily replicate by people typing it in or C+Ping it to each other.</htmltext>
<tokenext>Its not outside the realms of possibility... you make a bit of malicious code that hides in a very meme-y bit of text , then it can as easily replicate by people typing it in or C + Ping it to each other .</tokentext>
<sentencetext>Its not outside the realms of possibility... you make a bit of malicious code that hides in a very meme-y bit of text, then it can as easily replicate by people typing it in or C+Ping it to each other.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210882</id>
	<title>This is far more interesting!</title>
	<author>Terje Mathisen</author>
	<datestamp>1259095380000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext><p>I for one is very impressed by what they've done, even if it is somewhat similar to what I did nearly 15 years ago:</p><p>At that time I wrote what's probably the "best" executable text encoder for MsDos, it uses the absolute minimum possible amount of self-modification (a single 2-byte Jcc opcode) while staying entirely within the MIME text character set, and survives all the most usual forms of reformatting/reflowing of the text. (Replacing CRLF with a single CR (Mac) or LF (unix) or turning each paragraph into a single line.)</p><p>The initial bootstrap looks like this:</p><p>ZRYPQIQDYLRQRQRRAQX,2,NPPa,R0Gc,.0Gd,PPu.F2,QX=0+r+E=0=tG0-Ju E=<br>EE(-(-GNEEEEEEEEEEEEEEEF 5BBEEYQEEEE=DU.COM=======(c)TMathisen95</p><p>(The uppercase 'E's are my NOP fillers, they execute as INC BP, a register I don't use.)</p><p>Terje</p><p>PS. Unlike the current guys, I wrote the code above by hand, on paper, during the evenings of a ski vacation. I had brought with me a listing of the ascii encoding of all instructions that would use MIME characters only.<nobr> <wbr></nobr>:-)</p></htmltext>
<tokenext>I for one is very impressed by what they 've done , even if it is somewhat similar to what I did nearly 15 years ago : At that time I wrote what 's probably the " best " executable text encoder for MsDos , it uses the absolute minimum possible amount of self-modification ( a single 2-byte Jcc opcode ) while staying entirely within the MIME text character set , and survives all the most usual forms of reformatting/reflowing of the text .
( Replacing CRLF with a single CR ( Mac ) or LF ( unix ) or turning each paragraph into a single line .
) The initial bootstrap looks like this : ZRYPQIQDYLRQRQRRAQX,2,NPPa,R0Gc,.0Gd,PPu.F2,QX = 0 + r + E = 0 = tG0-Ju E = EE ( - ( -GNEEEEEEEEEEEEEEEF 5BBEEYQEEEE = DU.COM = = = = = = = ( c ) TMathisen95 ( The uppercase 'E 's are my NOP fillers , they execute as INC BP , a register I do n't use. ) TerjePS .
Unlike the current guys , I wrote the code above by hand , on paper , during the evenings of a ski vacation .
I had brought with me a listing of the ascii encoding of all instructions that would use MIME characters only .
: - )</tokentext>
<sentencetext>I for one is very impressed by what they've done, even if it is somewhat similar to what I did nearly 15 years ago:At that time I wrote what's probably the "best" executable text encoder for MsDos, it uses the absolute minimum possible amount of self-modification (a single 2-byte Jcc opcode) while staying entirely within the MIME text character set, and survives all the most usual forms of reformatting/reflowing of the text.
(Replacing CRLF with a single CR (Mac) or LF (unix) or turning each paragraph into a single line.
)The initial bootstrap looks like this:ZRYPQIQDYLRQRQRRAQX,2,NPPa,R0Gc,.0Gd,PPu.F2,QX=0+r+E=0=tG0-Ju E=EE(-(-GNEEEEEEEEEEEEEEEF 5BBEEYQEEEE=DU.COM=======(c)TMathisen95(The uppercase 'E's are my NOP fillers, they execute as INC BP, a register I don't use.)TerjePS.
Unlike the current guys, I wrote the code above by hand, on paper, during the evenings of a ski vacation.
I had brought with me a listing of the ascii encoding of all instructions that would use MIME characters only.
:-)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209342</id>
	<title>Re:In other news...Christmas gifts</title>
	<author>coolforsale122</author>
	<datestamp>1258988280000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><a href="http://www.coolforsale.com/" title="coolforsale.com" rel="nofollow">http://www.coolforsale.com/</a> [coolforsale.com]  Dear ladies and gentlemen Hello, In order to meet Christmas, Site launched Christmas spree, welcome new and old customers come to participate in the there are unexpected surprises, look forward to your arrival. Only this site have this treatmentOur goal is "Best quality, Best reputation , Best services". Your satisfaction is our main pursue. You can find the best products from us, meeting your different needs. Ladies and Gentlemen weicome to my coolforsale.com.Here,there are the most fashion products . Pass by but don't miss it.Select your favorite clothing! Welcome to come next time ! Thank you! <a href="http://www.coolforsale.com/productlist.asp?id=s76" title="coolforsale.com" rel="nofollow">http://www.coolforsale.com/productlist.asp?id=s76</a> [coolforsale.com]   (Tracksuit w) ugg boot,POLO hoody,Jacket, Air jordan(1-24)shoes $33 Nike shox(R4,NZ,OZ,TL1,TL2,TL3) $35 Handbags(Coach lv fendi d&amp;g) $35 Tshirts (Polo<nobr> <wbr></nobr>,ed hardy,lacoste) $16 free shipping Thanks!!! Advance wish you a merry Christmas.</htmltext>
<tokenext>http : //www.coolforsale.com/ [ coolforsale.com ] Dear ladies and gentlemen Hello , In order to meet Christmas , Site launched Christmas spree , welcome new and old customers come to participate in the there are unexpected surprises , look forward to your arrival .
Only this site have this treatmentOur goal is " Best quality , Best reputation , Best services " .
Your satisfaction is our main pursue .
You can find the best products from us , meeting your different needs .
Ladies and Gentlemen weicome to my coolforsale.com.Here,there are the most fashion products .
Pass by but do n't miss it.Select your favorite clothing !
Welcome to come next time !
Thank you !
http : //www.coolforsale.com/productlist.asp ? id = s76 [ coolforsale.com ] ( Tracksuit w ) ugg boot,POLO hoody,Jacket , Air jordan ( 1-24 ) shoes $ 33 Nike shox ( R4,NZ,OZ,TL1,TL2,TL3 ) $ 35 Handbags ( Coach lv fendi d&amp;g ) $ 35 Tshirts ( Polo ,ed hardy,lacoste ) $ 16 free shipping Thanks ! ! !
Advance wish you a merry Christmas .</tokentext>
<sentencetext>http://www.coolforsale.com/ [coolforsale.com]  Dear ladies and gentlemen Hello, In order to meet Christmas, Site launched Christmas spree, welcome new and old customers come to participate in the there are unexpected surprises, look forward to your arrival.
Only this site have this treatmentOur goal is "Best quality, Best reputation , Best services".
Your satisfaction is our main pursue.
You can find the best products from us, meeting your different needs.
Ladies and Gentlemen weicome to my coolforsale.com.Here,there are the most fashion products .
Pass by but don't miss it.Select your favorite clothing!
Welcome to come next time !
Thank you!
http://www.coolforsale.com/productlist.asp?id=s76 [coolforsale.com]   (Tracksuit w) ugg boot,POLO hoody,Jacket, Air jordan(1-24)shoes $33 Nike shox(R4,NZ,OZ,TL1,TL2,TL3) $35 Handbags(Coach lv fendi d&amp;g) $35 Tshirts (Polo ,ed hardy,lacoste) $16 free shipping Thanks!!!
Advance wish you a merry Christmas.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209832</id>
	<title>Re:In other news...</title>
	<author>QuantumG</author>
	<datestamp>1258993560000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>Whoever modded this up is a retard.</p><p>Let this post stand as an example of all that is wrong with the Slashdot moderation system.</p><p>Idiots.</p></htmltext>
<tokenext>Whoever modded this up is a retard.Let this post stand as an example of all that is wrong with the Slashdot moderation system.Idiots .</tokentext>
<sentencetext>Whoever modded this up is a retard.Let this post stand as an example of all that is wrong with the Slashdot moderation system.Idiots.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210480</id>
	<title>Re:OMG!</title>
	<author>elfprince13</author>
	<datestamp>1259002320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>hey man, you want to try some snow crash?</htmltext>
<tokenext>hey man , you want to try some snow crash ?</tokentext>
<sentencetext>hey man, you want to try some snow crash?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210158</id>
	<title>Re:Linux version</title>
	<author>TeamSPAM</author>
	<datestamp>1258997820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p> come on. if you're gonna help people shoot themselves in the foot, do it right:<br>rm -rf<nobr> <wbr></nobr>./*<br>location is important to.</p></htmltext>
<tokenext>come on .
if you 're gon na help people shoot themselves in the foot , do it right : rm -rf ./ * location is important to .</tokentext>
<sentencetext> come on.
if you're gonna help people shoot themselves in the foot, do it right:rm -rf ./*location is important to.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211338</id>
	<title>Perhaps Cockney English shell code could be used?</title>
	<author>fantomas</author>
	<datestamp>1259061540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Better security solution. Because me old china, even if a whole bunch of yer muckers take a butchers they won't have a scoobie about you're rabbitting on about.</p></htmltext>
<tokenext>Better security solution .
Because me old china , even if a whole bunch of yer muckers take a butchers they wo n't have a scoobie about you 're rabbitting on about .</tokentext>
<sentencetext>Better security solution.
Because me old china, even if a whole bunch of yer muckers take a butchers they won't have a scoobie about you're rabbitting on about.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209980</id>
	<title>Hello, World!</title>
	<author>nneonneo</author>
	<datestamp>1258995240000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>There is a major center of economic activity, such as Star Trek, including The Ed Sullivan Show. The former Soviet Union. International organization participation Asian Development Bank, established in the United States Drug Enforcement Administration, and the Palestinian territories, the International Telecommunication Union, the result of the collapse of large portions of the three provinces to have a syntax which can be found in the case of Canada and the UK, for the carriage of goods were no doubt first considered by the British, and the government, and the Soviet Union operated on the basis that they were the US Navys interpretation of the state to which he was subsequently influenced by the new government was established in 1951, when the new constitution approved it you King, he now had the higher than that the M.G.u, and soul shouters like Diane. There's a mama maggot including the major justifications that the test led to his own. This is usually prepared by the infection of the Sinai to the back and the Star Destroyers in the parliament, by the speed of these books and the revival of environmental problems of their new Arab states of the Arctic as a more and they possess power to the effort she was especially valuable as the Union and that would have said, as to note that the goods, which the night that if ever I rode after the word Father upon His Church to claim that the peace that had permitted him the city are as a hand of one into I thought of Mr. Crow and the Jews by the days of the C.Cs front garden which had first to St Cyriacus. All of a theology in the setting in a human heart as the tale of this day. I have it to friendship and the States that the way the English of the St Lawrence seven miles of an adjutant...</p><p>Now, would you have guessed that this is executable machine code (shellcode)? Honestly, it looks more like the garbage that spammers use to defeat statistical analysis (indeed, this is code generated with a similar goal).</p><p>(P.S. this particular sample is merely an amalgamation of the code which was reproduced in the paper; it is not complete, and will therefore not execute).</p></htmltext>
<tokenext>There is a major center of economic activity , such as Star Trek , including The Ed Sullivan Show .
The former Soviet Union .
International organization participation Asian Development Bank , established in the United States Drug Enforcement Administration , and the Palestinian territories , the International Telecommunication Union , the result of the collapse of large portions of the three provinces to have a syntax which can be found in the case of Canada and the UK , for the carriage of goods were no doubt first considered by the British , and the government , and the Soviet Union operated on the basis that they were the US Navys interpretation of the state to which he was subsequently influenced by the new government was established in 1951 , when the new constitution approved it you King , he now had the higher than that the M.G.u , and soul shouters like Diane .
There 's a mama maggot including the major justifications that the test led to his own .
This is usually prepared by the infection of the Sinai to the back and the Star Destroyers in the parliament , by the speed of these books and the revival of environmental problems of their new Arab states of the Arctic as a more and they possess power to the effort she was especially valuable as the Union and that would have said , as to note that the goods , which the night that if ever I rode after the word Father upon His Church to claim that the peace that had permitted him the city are as a hand of one into I thought of Mr. Crow and the Jews by the days of the C.Cs front garden which had first to St Cyriacus .
All of a theology in the setting in a human heart as the tale of this day .
I have it to friendship and the States that the way the English of the St Lawrence seven miles of an adjutant...Now , would you have guessed that this is executable machine code ( shellcode ) ?
Honestly , it looks more like the garbage that spammers use to defeat statistical analysis ( indeed , this is code generated with a similar goal ) . ( P.S .
this particular sample is merely an amalgamation of the code which was reproduced in the paper ; it is not complete , and will therefore not execute ) .</tokentext>
<sentencetext>There is a major center of economic activity, such as Star Trek, including The Ed Sullivan Show.
The former Soviet Union.
International organization participation Asian Development Bank, established in the United States Drug Enforcement Administration, and the Palestinian territories, the International Telecommunication Union, the result of the collapse of large portions of the three provinces to have a syntax which can be found in the case of Canada and the UK, for the carriage of goods were no doubt first considered by the British, and the government, and the Soviet Union operated on the basis that they were the US Navys interpretation of the state to which he was subsequently influenced by the new government was established in 1951, when the new constitution approved it you King, he now had the higher than that the M.G.u, and soul shouters like Diane.
There's a mama maggot including the major justifications that the test led to his own.
This is usually prepared by the infection of the Sinai to the back and the Star Destroyers in the parliament, by the speed of these books and the revival of environmental problems of their new Arab states of the Arctic as a more and they possess power to the effort she was especially valuable as the Union and that would have said, as to note that the goods, which the night that if ever I rode after the word Father upon His Church to claim that the peace that had permitted him the city are as a hand of one into I thought of Mr. Crow and the Jews by the days of the C.Cs front garden which had first to St Cyriacus.
All of a theology in the setting in a human heart as the tale of this day.
I have it to friendship and the States that the way the English of the St Lawrence seven miles of an adjutant...Now, would you have guessed that this is executable machine code (shellcode)?
Honestly, it looks more like the garbage that spammers use to defeat statistical analysis (indeed, this is code generated with a similar goal).(P.S.
this particular sample is merely an amalgamation of the code which was reproduced in the paper; it is not complete, and will therefore not execute).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209634</id>
	<title>I'm screwed</title>
	<author>Anonymous</author>
	<datestamp>1258991160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Since the first thing I do with all my emails is save the text and run it as a binary executable.</p></htmltext>
<tokenext>Since the first thing I do with all my emails is save the text and run it as a binary executable .</tokentext>
<sentencetext>Since the first thing I do with all my emails is save the text and run it as a binary executable.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486</id>
	<title>Re:This is</title>
	<author>afidel</author>
	<datestamp>1258989780000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>Isn't this what NX is supposed to stop, execution of arbitrary data as code?</htmltext>
<tokenext>Is n't this what NX is supposed to stop , execution of arbitrary data as code ?</tokentext>
<sentencetext>Isn't this what NX is supposed to stop, execution of arbitrary data as code?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212518</id>
	<title>Re:Linux version</title>
	<author>selven</author>
	<datestamp>1259071440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Don't you mean<br>sudo rm -rf /</htmltext>
<tokenext>Do n't you meansudo rm -rf /</tokentext>
<sentencetext>Don't you meansudo rm -rf /</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210864</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211576</id>
	<title>Re:This is</title>
	<author>Anonymous</author>
	<datestamp>1259063640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>What is "shell code" supposed to be?  Bourne shell scripts?</p></htmltext>
<tokenext>What is " shell code " supposed to be ?
Bourne shell scripts ?</tokentext>
<sentencetext>What is "shell code" supposed to be?
Bourne shell scripts?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211508</id>
	<title>Why run the code?</title>
	<author>Anonymous</author>
	<datestamp>1259063280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've skimmed the article, but I still don't get the idea of this.</p><p>I understand the part where machine-language is carefully crafted so that the bytes resemble ASCII text. But how is this an exploit? Why should I take an email that has somehow evaded my spam filter (despite reading like utter gibberish), save it to a file on my local machine, and run that file as an executable? Even if I wanted to run arbitrary code from an unknown third party, how would I even know that the contents of this email consisted of code in the first place? Could someone explain what I'm missing here?</p></htmltext>
<tokenext>I 've skimmed the article , but I still do n't get the idea of this.I understand the part where machine-language is carefully crafted so that the bytes resemble ASCII text .
But how is this an exploit ?
Why should I take an email that has somehow evaded my spam filter ( despite reading like utter gibberish ) , save it to a file on my local machine , and run that file as an executable ?
Even if I wanted to run arbitrary code from an unknown third party , how would I even know that the contents of this email consisted of code in the first place ?
Could someone explain what I 'm missing here ?</tokentext>
<sentencetext>I've skimmed the article, but I still don't get the idea of this.I understand the part where machine-language is carefully crafted so that the bytes resemble ASCII text.
But how is this an exploit?
Why should I take an email that has somehow evaded my spam filter (despite reading like utter gibberish), save it to a file on my local machine, and run that file as an executable?
Even if I wanted to run arbitrary code from an unknown third party, how would I even know that the contents of this email consisted of code in the first place?
Could someone explain what I'm missing here?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211824</id>
	<title>0x20</title>
	<author>Anonymous</author>
	<datestamp>1259065860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>0x20 Space is AND?</p><p>That's surreal! It's almost as if x86 were designed for this! O\_O</p></htmltext>
<tokenext>0x20 Space is AND ? That 's surreal !
It 's almost as if x86 were designed for this !
O \ _O</tokentext>
<sentencetext>0x20 Space is AND?That's surreal!
It's almost as if x86 were designed for this!
O\_O</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796</id>
	<title>Linux version</title>
	<author>Anonymous</author>
	<datestamp>1258993020000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>They also came up with a Linux version, which even works on non-x86 architectures, all the while looking like plain English:

<p>"Please type the following on your command-line:

</p><p>rm -rf *

</p><p>Thank you."</p></htmltext>
<tokenext>They also came up with a Linux version , which even works on non-x86 architectures , all the while looking like plain English : " Please type the following on your command-line : rm -rf * Thank you .
"</tokentext>
<sentencetext>They also came up with a Linux version, which even works on non-x86 architectures, all the while looking like plain English:

"Please type the following on your command-line:

rm -rf *

Thank you.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209736</id>
	<title>We're doomed!</title>
	<author>REggert</author>
	<datestamp>1258992300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Oh noes!  If only we had a way to detect and filter text that looks like spam....</p></htmltext>
<tokenext>Oh noes !
If only we had a way to detect and filter text that looks like spam... .</tokentext>
<sentencetext>Oh noes!
If only we had a way to detect and filter text that looks like spam....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209288</id>
	<title>This very comment</title>
	<author>ewg</author>
	<datestamp>1258987860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Why, this very comment prints a list of prime numbers less than one hundred!</htmltext>
<tokenext>Why , this very comment prints a list of prime numbers less than one hundred !</tokentext>
<sentencetext>Why, this very comment prints a list of prime numbers less than one hundred!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209414</id>
	<title>oblig</title>
	<author>Anonymous</author>
	<datestamp>1258988940000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Has anyone really been far even as decided to use even go want to do look more like?</p></htmltext>
<tokenext>Has anyone really been far even as decided to use even go want to do look more like ?</tokentext>
<sentencetext>Has anyone really been far even as decided to use even go want to do look more like?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554</id>
	<title>Re:This is</title>
	<author>mysidia</author>
	<datestamp>1258990380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>
I propose the x86 instruction set be altered to add an additional byte to every instruction, a NUL byte or NUL word, so every instruction will have an additional 2 to 8 bytes of overhead, at least 1 must be set to all bits 0, and the following byte must be set to all bits 1.
</p><p>
Since the NUL byte cannot be expressed in a sentence and commonly causes I/O to terminate (i.e. delineates the end of the string),  x86 code can then not be disguised as a sentence.
</p><p>
Also, the following byte being all bits 1, assures that  the instruction cannot be transmitted over protocols that do not provide 8-bit support.
</p><p>
Further, the all-bits 1 sequence should be removed from ASCII and banned from use by any network protocol:  to transmit such bits, you must encode in Base64.
</p></htmltext>
<tokenext>I propose the x86 instruction set be altered to add an additional byte to every instruction , a NUL byte or NUL word , so every instruction will have an additional 2 to 8 bytes of overhead , at least 1 must be set to all bits 0 , and the following byte must be set to all bits 1 .
Since the NUL byte can not be expressed in a sentence and commonly causes I/O to terminate ( i.e .
delineates the end of the string ) , x86 code can then not be disguised as a sentence .
Also , the following byte being all bits 1 , assures that the instruction can not be transmitted over protocols that do not provide 8-bit support .
Further , the all-bits 1 sequence should be removed from ASCII and banned from use by any network protocol : to transmit such bits , you must encode in Base64 .</tokentext>
<sentencetext>
I propose the x86 instruction set be altered to add an additional byte to every instruction, a NUL byte or NUL word, so every instruction will have an additional 2 to 8 bytes of overhead, at least 1 must be set to all bits 0, and the following byte must be set to all bits 1.
Since the NUL byte cannot be expressed in a sentence and commonly causes I/O to terminate (i.e.
delineates the end of the string),  x86 code can then not be disguised as a sentence.
Also, the following byte being all bits 1, assures that  the instruction cannot be transmitted over protocols that do not provide 8-bit support.
Further, the all-bits 1 sequence should be removed from ASCII and banned from use by any network protocol:  to transmit such bits, you must encode in Base64.
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209340</id>
	<title>Re:Confused</title>
	<author>blueg3</author>
	<datestamp>1258988280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Shellcode is machine code. That is, compiled assembler.</p><p>It's just a logical extension of the shellcode filters that Metasploit already provides. If you hadn't thought it through, though, it's an important proof-of-concept.</p></htmltext>
<tokenext>Shellcode is machine code .
That is , compiled assembler.It 's just a logical extension of the shellcode filters that Metasploit already provides .
If you had n't thought it through , though , it 's an important proof-of-concept .</tokentext>
<sentencetext>Shellcode is machine code.
That is, compiled assembler.It's just a logical extension of the shellcode filters that Metasploit already provides.
If you hadn't thought it through, though, it's an important proof-of-concept.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211252</id>
	<title>Re:Antelope museum</title>
	<author>Anonymous</author>
	<datestamp>1259059020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Help my mouse is moving itself</p></htmltext>
<tokenext>Help my mouse is moving itself</tokentext>
<sentencetext>Help my mouse is moving itself</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209844</id>
	<title>Re:Antelope museum</title>
	<author>Tablizer</author>
	<datestamp>1258993680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Steamed cabbage can reverse big piles of ducks.</p></div></blockquote><p>I have ways to mod you to 10 if you can produce a Youtube vid of that.<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;</p></div>
	</htmltext>
<tokenext>Steamed cabbage can reverse big piles of ducks.I have ways to mod you to 10 if you can produce a Youtube vid of that .
         </tokentext>
<sentencetext>Steamed cabbage can reverse big piles of ducks.I have ways to mod you to 10 if you can produce a Youtube vid of that.
         
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209966</id>
	<title>Re:This is UNICODE</title>
	<author>Anonymous</author>
	<datestamp>1258995000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Mysidia is making a sarcastic reference to UNICODE; wooosh...</p></htmltext>
<tokenext>Mysidia is making a sarcastic reference to UNICODE ; wooosh.. .</tokentext>
<sentencetext>Mysidia is making a sarcastic reference to UNICODE; wooosh...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30223718</id>
	<title>Re:This is</title>
	<author>perew</author>
	<datestamp>1257154200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Computer architectures have existed since at least the early 60s which strictly segregate data from authorized instructions.  The original Burroughs B5000 systems, and its modern descendants, the Unisys Clearpath MCP Libra Series, are immune to this kind of attack.  It's a shame that the world has adopted the far inferior x86 architecture.</htmltext>
<tokenext>Computer architectures have existed since at least the early 60s which strictly segregate data from authorized instructions .
The original Burroughs B5000 systems , and its modern descendants , the Unisys Clearpath MCP Libra Series , are immune to this kind of attack .
It 's a shame that the world has adopted the far inferior x86 architecture .</tokentext>
<sentencetext>Computer architectures have existed since at least the early 60s which strictly segregate data from authorized instructions.
The original Burroughs B5000 systems, and its modern descendants, the Unisys Clearpath MCP Libra Series, are immune to this kind of attack.
It's a shame that the world has adopted the far inferior x86 architecture.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210132</id>
	<title>Re:This is</title>
	<author>Anonymous</author>
	<datestamp>1258997580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The obvious question at hand..</p><p>Does this kind of double meaning for the resulting text get double copyright protection?</p><p>Considering that the resut is a "Literary work", as well as a computer program...</p><p>It could also add a whole new dimension to the term "Viral advertising"...</p></htmltext>
<tokenext>The obvious question at hand..Does this kind of double meaning for the resulting text get double copyright protection ? Considering that the resut is a " Literary work " , as well as a computer program...It could also add a whole new dimension to the term " Viral advertising " .. .</tokentext>
<sentencetext>The obvious question at hand..Does this kind of double meaning for the resulting text get double copyright protection?Considering that the resut is a "Literary work", as well as a computer program...It could also add a whole new dimension to the term "Viral advertising"...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209358</id>
	<title>Re:This is</title>
	<author>Wovel</author>
	<datestamp>1258988400000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>Guess you missed their "compromised" machine assumption.  "..After successful exploitation of a software vulnerability, we assume that a pointer to the shellcode..." .  The sky is not really falling any faster today than it was yesterday.</p></htmltext>
<tokenext>Guess you missed their " compromised " machine assumption .
" ..After successful exploitation of a software vulnerability , we assume that a pointer to the shellcode... " .
The sky is not really falling any faster today than it was yesterday .</tokentext>
<sentencetext>Guess you missed their "compromised" machine assumption.
"..After successful exploitation of a software vulnerability, we assume that a pointer to the shellcode..." .
The sky is not really falling any faster today than it was yesterday.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209320</id>
	<title>Re:Confused</title>
	<author>icebraining</author>
	<datestamp>1258988100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>It's a <a href="http://en.wikipedia.org/wiki/Shellcode" title="wikipedia.org">shellcode</a> [wikipedia.org]; it's actually written in machine code.</p></htmltext>
<tokenext>It 's a shellcode [ wikipedia.org ] ; it 's actually written in machine code .</tokentext>
<sentencetext>It's a shellcode [wikipedia.org]; it's actually written in machine code.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210268</id>
	<title>Slap me five</title>
	<author>Anonymous</author>
	<datestamp>1258999380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Great. I'll look forward to installing McAfee Jive.</p></htmltext>
<tokenext>Great .
I 'll look forward to installing McAfee Jive .</tokentext>
<sentencetext>Great.
I'll look forward to installing McAfee Jive.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30218396</id>
	<title>Re:OMG!</title>
	<author>Anonymous</author>
	<datestamp>1259056080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I haven't seen weather like this since I was a kid in Ohio.</p></htmltext>
<tokenext>I have n't seen weather like this since I was a kid in Ohio .</tokentext>
<sentencetext>I haven't seen weather like this since I was a kid in Ohio.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210778</id>
	<title>Obvious meatspace vector:</title>
	<author>DamnStupidElf</author>
	<datestamp>1259093700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>"MZBlahBlah...  Hello, please save the text of this email as blahblah.pif and open it to enable the images/porn/bonzai buddy/whatever you think is important enough to go through minor hoops to get"</htmltext>
<tokenext>" MZBlahBlah... Hello , please save the text of this email as blahblah.pif and open it to enable the images/porn/bonzai buddy/whatever you think is important enough to go through minor hoops to get "</tokentext>
<sentencetext>"MZBlahBlah...  Hello, please save the text of this email as blahblah.pif and open it to enable the images/porn/bonzai buddy/whatever you think is important enough to go through minor hoops to get"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213070</id>
	<title>Re:OMG!</title>
	<author>Migala77</author>
	<datestamp>1259074620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Now your brain can catch a virus just by reading!!!1</p></div><p>Nothing new there... check <a href="http://en.wikipedia.org/wiki/Cultural\_references\_to\_the\_novel\_The\_Catcher\_in\_the\_Rye#Shootings" title="wikipedia.org" rel="nofollow">The Catcher in the Rye</a> [wikipedia.org]</p></div>
	</htmltext>
<tokenext>Now your brain can catch a virus just by reading ! !
! 1Nothing new there... check The Catcher in the Rye [ wikipedia.org ]</tokentext>
<sentencetext>Now your brain can catch a virus just by reading!!
!1Nothing new there... check The Catcher in the Rye [wikipedia.org]
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210316</id>
	<title>Apple already did this</title>
	<author>syousef</author>
	<datestamp>1258999980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>If hackers convert arbitrary x86 shell code into sentences that read like spam, but are natively executable<nobr> <wbr></nobr>.. we're all screwed<nobr> <wbr></nobr>:(</i></p><p>It's called Hypercard.</p></htmltext>
<tokenext>If hackers convert arbitrary x86 shell code into sentences that read like spam , but are natively executable .. we 're all screwed : ( It 's called Hypercard .</tokentext>
<sentencetext>If hackers convert arbitrary x86 shell code into sentences that read like spam, but are natively executable .. we're all screwed :(It's called Hypercard.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210160</id>
	<title>Re:OMG!</title>
	<author>Concerned Onlooker</author>
	<datestamp>1258997880000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Yes, its' a simple head code.  Any English schoolboy could catch it.</p></htmltext>
<tokenext>Yes , its ' a simple head code .
Any English schoolboy could catch it .</tokentext>
<sentencetext>Yes, its' a simple head code.
Any English schoolboy could catch it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209794</id>
	<title>So what?</title>
	<author>Fnord666</author>
	<datestamp>1258993020000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I guess I don't see the big deal in this paper.  Yes, they can encode the shell code into English sentences.  It's still meaningless to the recipient and should raise suspicion.  It would be far easier to use simple steganographic techniques to embed the shell code into any image transmitted between two systems.  The recipient would not suspect any alteration and filters would not have the original image for comparison.  Just a thought.  Maybe I should write a response paper.</htmltext>
<tokenext>I guess I do n't see the big deal in this paper .
Yes , they can encode the shell code into English sentences .
It 's still meaningless to the recipient and should raise suspicion .
It would be far easier to use simple steganographic techniques to embed the shell code into any image transmitted between two systems .
The recipient would not suspect any alteration and filters would not have the original image for comparison .
Just a thought .
Maybe I should write a response paper .</tokentext>
<sentencetext>I guess I don't see the big deal in this paper.
Yes, they can encode the shell code into English sentences.
It's still meaningless to the recipient and should raise suspicion.
It would be far easier to use simple steganographic techniques to embed the shell code into any image transmitted between two systems.
The recipient would not suspect any alteration and filters would not have the original image for comparison.
Just a thought.
Maybe I should write a response paper.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30214302</id>
	<title>Re:This is</title>
	<author>mcgrew</author>
	<datestamp>1259080740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>The sky is not really falling any faster today than it was yesterday</i></p><p>Yes it is, here anyway. Yesterday it was sunny, today it's raining.</p></htmltext>
<tokenext>The sky is not really falling any faster today than it was yesterdayYes it is , here anyway .
Yesterday it was sunny , today it 's raining .</tokentext>
<sentencetext>The sky is not really falling any faster today than it was yesterdayYes it is, here anyway.
Yesterday it was sunny, today it's raining.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209358</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209384</id>
	<title>Re:OMG!</title>
	<author>enoz</author>
	<datestamp>1258988640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The English language is infected, do not translate this message.</p></htmltext>
<tokenext>The English language is infected , do not translate this message .</tokentext>
<sentencetext>The English language is infected, do not translate this message.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209208</id>
	<title>The syntax should not matter..</title>
	<author>Wovel</author>
	<datestamp>1258987260000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>-1</modscore>
	<htmltext><p>This is no different than adding any other shell...If your security is relying on an inline inspection for commands specific to a particular shell, you have already lost.</p></htmltext>
<tokenext>This is no different than adding any other shell...If your security is relying on an inline inspection for commands specific to a particular shell , you have already lost .</tokentext>
<sentencetext>This is no different than adding any other shell...If your security is relying on an inline inspection for commands specific to a particular shell, you have already lost.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212492</id>
	<title>YAWN</title>
	<author>Anonymous</author>
	<datestamp>1259071320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Let me know when I can simply send someone an email with the text "open goatse" and it has the desired effect of opening a browser window and surfing to goatse.</p></htmltext>
<tokenext>Let me know when I can simply send someone an email with the text " open goatse " and it has the desired effect of opening a browser window and surfing to goatse .</tokentext>
<sentencetext>Let me know when I can simply send someone an email with the text "open goatse" and it has the desired effect of opening a browser window and surfing to goatse.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580</id>
	<title>Antelope museum</title>
	<author>beej</author>
	<datestamp>1258990620000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Consume more trains, Elvis! He, and snorkels, drink elephant's sock puppet master.  Steamed cabbage can reverse big piles of ducks. Additionally, cheese log cabin nightmare.</p><p>You're screwed now, x86 suckas!</p></htmltext>
<tokenext>Consume more trains , Elvis !
He , and snorkels , drink elephant 's sock puppet master .
Steamed cabbage can reverse big piles of ducks .
Additionally , cheese log cabin nightmare.You 're screwed now , x86 suckas !</tokentext>
<sentencetext>Consume more trains, Elvis!
He, and snorkels, drink elephant's sock puppet master.
Steamed cabbage can reverse big piles of ducks.
Additionally, cheese log cabin nightmare.You're screwed now, x86 suckas!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209940</id>
	<title>i just got off the toilet</title>
	<author>Anonymous</author>
	<datestamp>1258994880000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>i just shit out an obama.<br> <br>plop!</htmltext>
<tokenext>i just shit out an obama .
plop !</tokentext>
<sentencetext>i just shit out an obama.
plop!</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212816
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209384
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30214302
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209358
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213498
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211508
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211934
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209688
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211576
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211202
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213178
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212844
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209510
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209324
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210882
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211092
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210070
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30223718
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210114
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209340
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209718
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209320
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30215450
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210654
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209844
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210992
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209886
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209550
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213508
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209270
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209208
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210316
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209598
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30216142
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210160
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212518
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210864
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210158
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213070
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209832
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210744
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209288
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30220392
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209794
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210312
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212762
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210040
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210346
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210480
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209280
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211056
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209948
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210078
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209342
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209676
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30218396
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211252
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209966
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210132
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212492
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_11_23_1837238_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211278
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209324
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209510
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209776
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209706
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209258
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209320
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209718
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209340
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210070
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209980
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209288
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210744
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211338
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209196
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209832
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209342
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210078
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210882
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209208
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209270
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209796
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212816
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210158
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210864
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212518
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213178
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209580
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210312
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211934
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210040
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210654
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211092
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209844
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209688
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211252
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211508
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213498
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209736
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209474
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209950
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209794
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30220392
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209302
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210480
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30218396
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209384
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210160
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30216142
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211278
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209598
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213070
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209948
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211056
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209232
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209212
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211202
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210346
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30215450
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210316
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209676
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212844
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209358
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30214302
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209486
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209550
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209886
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210992
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30213508
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30223718
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210114
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209554
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212762
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209966
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30211576
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30210132
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30212492
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209280
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_11_23_1837238.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_11_23_1837238.30209634
</commentlist>
</conversation>
