EvilZone

Ok, what powerful cards do you suggest?

Some more experienced wardriver might correct the suggestion, but I found the Realtek RTL8187L chip of my old AWUS036H to be quite convenient. If I remember correctly, I attached a 9dBi antenna to it - only for randomly screwing around, nothing special/serious. However, it served the purpose very well 

But since I don't know much about atheros hardware, I couldn't even tell if the 87L would be an up- or downgrade for you. Please note that I am no expert in the field :x

Pick a certain topic that attracts you the most and google the fuck out of it. There are tons of eBooks waiting for you, so just grab one and start reading! (-> https://evilzone.org/ebooks/ <-)
Besides, make sure to check out the tut section of this forum, some threads will surely leap to your eye and give you ideas of all dem fancy possibilities
When it comes to coding, take some general-purpose + beginner-friendly programming language and then rape google with it (although I'd suggest C++ or Python, you might want to generally avoid the common "omg-which-language-first" hysteria. Don't ponder too much, just pick one and start); plenty of great tutorials are right outta there, you absolutely can't miss em. Afterwards, read foreign code of works you'd love to call your own (but better don't actually do that), analyze em line-by-line(again: giyf!), and don't even dare to compile shit until you didn't get the whole point of each single statement. Go on like that until your brain finally produces something useful.

Summarized, I guess it is all about two simple core abilities:
Being able to 1. use search engines properly
and 2. entertain yourself without using your glans
Like that, shit keeps rolling on its own like nothing

Here's a little help on step one: https://evilzone.org/hacking-and-security/where-to-start-with-hacking/

well spoken, but

spend days learning how to solve it

tends to be my definite understanding of NOT being lazy.
It's all a matter of view points, I guess. Some ppl say "it's not 'work', if you enjoy shit", but I'd disagree to that. Solving problems actually IS work, it's a whole shitload of; and true senses of pleasure mostly approach afterwards, i.e. after succeeding. But the solving process itself usually requires quite decent abilities of the "argh, shit drives me insane, but I'll never surrender for fucking reposes sake" kind. You know.
My POV.

Any ideas how I can make use of it?
I consider any ideas, joint development or even sources sale

The source of a simple packet processing lib which is so incredible useless that even its creator needs help to find a reasonable purpose for it? Take all my money.


Dude, this is the programming subforum of a hacking community. Show your code or gtfo

Core War is a programming game created by D. G. Jones and A. K. Dewdney in which two or more battle programs (called "warriors") compete for control of a virtual computer. These battle programs are written in an abstract assembly language called Redcode. At the beginning of a game, each battle program is loaded into memory at a random location, after which each program executes one instruction in turn. The object of the game is to cause the processes of opposing programs to terminate (which happens if they execute an invalid instruction), leaving the victorious program in sole possession of the machine.

full article: http://en.wikipedia.org/wiki/Core_War
You may find interesting that the game's direct predecessor, 'Darwin', was written "around 1966 [by] Robert Morris, Sr., the future National Security Agency (NSA) chief scientist." (quoting "The art of virus research and defense" by Peter Szor, chapter 1.1.4)


Sounds pretty amazing, imo. Is anyone of you into this?

I discovered core war's existence only a few days ago, and therefore couldn't check it out by myself yet. But I will, since it might be some epic chess-like shit with the possibilty of programming your own game tokens. (Insert evil laughter here)

1) Stop being lazy.
2) Write code.
3) Write more code.
4) Go back and look at the awful code you wrote in step 2. Unfuck it. Make it faster. Make it use less memory. Make it more secure. If it's a script, make it OOP. If it's OOP, try to make it procedural.
5) Repeat.


If you're stuck on the bullshit tutorials, pick something you're interested in and write a program that involves that subject. Make a system to catalog your music/movie/porn collection. Write a browser plugin that downloads YouTube videos, whatever. If you find yourself doing the same repetitive task, figure out how to automate it. It doesn't really matter what you write, just write code.


As a corollary to that last statement, try googling "best way to <do something> in <language>". Look at the options, and don't settle for the first half-assed answer you see. While that's fine for prototyping or getting your feet wet, there are often lots of problems with the basic examples. Find a faster, better, more secure way of doing it. Then, test that shit and find what breaks, and fix it. Supply invalid input. Break things, fix them, then learn how to prevent them from breaking again.


The answers are out there - you may have to search for specific answers, but you can pretty much write any program in any language by searching StackOverflow and the likes. Just google it.


"how to save to a file in <language>"
"how to parse HTML in <language>"
etc.




Learning a computer language is just like learning any other language. You can sit in class, read about it, and wish you were fluent all day long, but until you get out there and start using it, you'll never know shit.

Decent as fuck. Beware, I'll pitch that cookie hard

Tool - 10000 Days album -> https://www.youtube.com/watch?v=7Ajx-ABtbVM
over and over