Talk:Shellcode
From Wikipedia, the free encyclopedia
Contents |
[edit] Article's accuracy?
This article is inaccurate. 'Shellcodes' are assembly-language programs which execute shells. They are typically inserted via techniques such as stack overflows, heap overflows, and format string attacks.
The shellcode itself does not exploit anything, it is simply a payload.
I'd be happy to take a first cut at rewriting this article, but a major rewrite is in order IMO, and I'm not sure what rules of etiquette apply here.
What do you mean with "and I'm not sure what rules of etiquette apply here."? Make the changes that you find is needed, and everyone will be happy, including the author :b! 193.11.232.248 21:19, 6 Sep 2004 (UTC)
[edit] First attempt at cleanup
OK, I took my first shot at cleanup. I fixed the incorrect information.
Much material belonged in buffer_overflow, and was better covered there, so I deleted those sections.
This isn't perfect by any means, but is a good start IMO. Any/all comments welcome
I plan to add more details on specific shellcodes (such as the Aleph One shellcode) at some point
Econrad 00:37, 20 Sep 2004 (UTC)
[edit] Major overhaul needed
When I read this, I thought there was alot of irrelevant information that had nothing to do with shellcode directly and had more to do with specific exploit types or computer architectures. I want to try and focus the article purely on shellcodes and how they relate to computer security in general.
I will remove any material that should be in other places and try to replace it with concise and relevant links.
 |
Please expand this article. Further information might be found in a section of the talk page or at Requests for expansion. |
Tompsci 13:45, 21 December 2005 (UTC)
[edit] Cracker
I think the use of the word "cracker" is wrong here, perhaps "attacker", "intruder" or similar. My point is that the person exploiting the system might not be a malicious "blackhat/cracker", but might aswell be a penetration tester, system administrator, software developer...
