Hacking

Hi, do you need very highskills like programming to hack some smaller sites for example?

I have no idea how to do it at all.

Are there some manuals for beginners? What tools do you need for?

Or better just demonstrating pages, where you can test you hacking skills (of course for very beginners;) ?

How do I 1337 hax pl0x?

hello im fairX the haxxor join my community of hackers if you payme enough i will give you access to a private area of haxx ;)
 
http://forum.curse-x.com/index.php

Again, someone who came here because of HACKERS ON STEROIDS

>>1,2,4
want to talk whit me?
Teamspeak server ts.curse-x.com:9797
Dont use guest names!
www.goteamspeak.com/downloads.php

Everything you need to know about hacking is in the movie "Hackers"

>>6
i lol'd
that movie is terrible

I think to be able to "hack" you need certain tools.

Don't know where you get it from though.

I wish i have more pc-skill too.

I think there a even books how to hack :)xD

>>1
The first rule of hacking is you do not ask questions about hacking.
Not being a fucktard helps too.

#9 true^^

But aren't there example servers/sites which are designed to test the skill of oneself.
So somehow like see if you can intrude the system etc.

Something like that must exists for beginners too, or?

>>10
Yes, a number of such projects exist.

Your first task would be finding them.

if 4failchan is such leet haxzr then crack my ip address:

http://211.248.156.177

i need help in hackin sumones myspace, any links for helpin me on this?

http://www.google.com/

a more spicific link please... im trying google just now, its just comin up with ppl askin how 2 do it but no answers

>>13
http://www.google.com/search?hl=en&q=phishing

>>12

Has someone already "hacked" into his PC?

I mean persons with 1337.skills should be able to do it.

>>12

Or mine:
http://127.139.82.103

>>17
STOP WATCHING MOVIES!

HACK MY GIBSON!
http://127.0.0.1

>>19 So you say it is impossible or?

ITT we make fun out of a wannabe scriptkiddie

wannabe script kiddie = fail of a fail

>>23
Does failing at failing constitute success?

>>24
Nope.  That's just more fail.  Fails are additive (f+f), at best.  Often they multiply (fxf).  In uncommon cases, they exponentiate (f^f).  In rare instances, the tetration operator comes into play (^ff, or "f^^f").  Woosh!  You don't want to go there, man!

step 1 access driver,, google for it
step 2

step 1 access driver,, google for it
step 2 get a proxy list
step 3 get a word list
step 4 import both lists to access drivers and profit???????

>>26
,(macro-faggotry)

>>27 for real? thanks........^^

>>1
So you wanna be a hacker? You pretty much failed already to become one by being stupid enough to post this question here. LEARN LEARN LEARN LEARN. If you cannot do that, you FAIL. The kids who 'want to become a hacker' always fail like this. This is because they do not have a real interest in technology, but just think that if they learn how to hack, it makes them special or cool. They quickly lose interest. Just learn about computers, that's pretty much the only usefull advice anyone can give to you.

>>30 i think you are right ;)

HOW TO HACK IN 5 EASY STEPS:

1. GREAT REALIZATION I: Realize that anything, ANYTHING that has to do with software, computers, or anything "digital" is reducible to lists of bytes, i.e. lists of numbers that can range from 0 to 255.  "Anything" means just that, programs, data, etc.
2. Learn about all the hardware and hardware systems you can, down to the schematic level if possible.  Nothing gets in and out of hardware without some sort of communication protocol. which is usually how software and hardware are connected.  So especially study hardware's communication protocols.  You aren't done with this step until you can build a multi-core superscalar CPU with built-in memory controller and video hardware from sand off the beach and wires scavenged from broken, old televisions.
3. Learn about all the data formats and programming languages you can.  Including assembly.  You aren't done with this step until you can write a 100% bug-free C compiler in assembly for ALL currently available CPUs.
4. GREAT REALIZATION II: Realize that writing programs and designing systems that do exactly what the programmer wants without intended side effects is generally an impossible feat, given the sheer complexity of 2 and 3. 
5. Once you have truly achieved the two Great Realizations, if the knowledge you've pursued in 2 and 3 are sufficient, then you can "hack."

IT'S THAT EASY!

>>32
 
Wow, i am speechless :)

How to hack: 

Learn every goddamn thing about computers that you possibly can.  By the time you've gotten about a quarter of the way through that, you'll know what you need to know (or at least know what you need to learn).

Also:  FUCKING GOOGLE FOR THE LOVE OF FUCK GOOGLE GOOGLE GOOGLE

DASU DASU DASU

>>32
don't forget to learn to love maths and mathematical logic. this would belong with step 1.

become familiar with RUN and CMD Prompt

GTFO newfag, gb2 /fox/

>>1 Collage was pretty fucking useless for you wasn't it...

hack my ip to test ur sk!llZ
my ip iz: 127.0.0.1

ping 127.0.0.1 -65509

gg