-
Best Online Casino Reviews
Distance: 0.0 Mi1461A 1st Ave
10075-2201 New York -
Navizon
Distance: 0.2 Mi304 E 79th St
10075-0926 New York -
Aardvark Software, Inc.
Distance: 0.2 Mi399 E 72 St Ste 18A
10021 New York -
Machintas Inc.
Distance: 0.3 Mi222 E80 St
10075 New York -
Subtle Investigations
Distance: 0.4 Mi303 E 83rd St Apt 28C
10028-4323 New York
hakin9 IT Security Magazine
- 1461A First Ave Ste 360
- New York, New York
- 11724-2203
- Phone: 917.338.3631
- Website
Website Links
Description
Of course, you can. hakin9 magazine is open to the external submissions. All that counts when submitting a paper is what you know and how well you explain things to the others. Please, read further for more guidelines. Please read also the information for authors to find out more. What kind of articles does hakin9 look for? The idea of hakin9 is to give the readers theory through practice. All our articles are written with that in mind, and so should be yours. If you're wondering what theory through practice means, try to follow the rules: -Do not try to write an RFC. RFCs are also good examples of theory through theory. -Do not try to write a program with comments. Programs with comments (even if they are better than the ones without comments...) are examples of practice through practice. Too little theoretical background is often available in the comments for the user to understand exactly what the program does. -Our articles can be compared to tutorials or howtos rather. These are examples of theory through practice!!! So, a good article for hakin9 should meet the following demands: Be based on a practical, working example. Say, you'd like to explain how buffer overflow works in hakin9 (it has been explained already, so treat this only as an example). Start by a simple example of a vulnerable program, three-four lines. Then, show step by step what happens when you overflow the buffer. Use diagrams, use snippets of code, use memory dumps. Use everything you need to show the reader exactly what happens on every stage. If you need to go off into theory, use an inset (a box on the side) to explain some ideas, so that the reader doesn't wonder off with his thoughts. Finally, find a program with a buffer overflow (eg. on bugtraq) and show that the same thing can be applied to this program, step by step.