It was developed in 1969 beginning with RFC 15 and standardized as IETFSTD 8, one
of the first Internet standards. The term telnet also refers to software which implements
the client part of the protocol. TELNET clients have been available on
most Unix systems for many years and are available for virtually all platforms.
Most network equipment and OSs with a TCP/IP stack support some kind of TELNET
service server for their remote configuration (including ones based on Windows NT).
Recently, Secure Shell has begun to dominate remote access for Unix-based machines. "To telnet" is also used as a verb meaning to establish or use a TELNET or other interactive
TCP connection,as in, "To change your password, telnet to the server and run the passwd command". Most often, a user will be telneting to a Unix-like server systemor a simple network device such as a switch.
For example, a user might "telnet in from home to check his mail at school".
In doing so, he would be using a telnet client to connect from his computer to one of his servers.
Once the connection is established, he would then log in with his account information and
execute operating system commands remotely on that computer, such as ls or cd. On many systems, the client may also be used to make interactive raw-TCP sessions,
even when that option is not available,
telnet sessions are equivalent to raw TCP as long as byte 255 never appears in the data.
What Is A Hacker? The Jargon File contains a bunch of definitions of the term `hacker', most having to do with technical adeptness and a delight in solving problems and overcoming limits. If you want to know how to become a hacker, though, only two are really relevant. There is a community, a shared culture, of expert programmers and networking wizards that traces its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture originated the term `hacker'. Hackers built the Internet. Hackers made the Unix operating system what it is today. Hackers run Usenet. Hackers make the World Wide Web work. If you are part of this culture, if you have contributed to it and other people in it know who you are and call you a hacker, you're a hacker.
The hacker mind-set is not confined to this software-hacker culture. There are people who apply the hacker attitude to other things, like electronics or music -- actually, you can find it at the highest levels of any science or art. Software hackers recognize these kindred spirits elsewhere and may call them "hackers" too -- and some claim that the hacker nature is really independent of the particular medium the hacker works in. But in the rest of this document we will focus on the skills and attitudes of software hackers, and the traditions of the shared culture that originated the term `hacker'.
There is another group of people who loudly call themselves hackers, but aren't. These are people (mainly adolescent males) who get a kick out of breaking into computers and phreaking the phone system. Real hackers call these people `crackers' and want nothing to do with them. Real hackers mostly think crackers are lazy, irresponsible, and not very bright, and object that being able to break security doesn't make you a hacker any more than being able to hotwire cars makes you an automotive engineer. Unfortunately, many journalists and writers have been fooled into using the word `hacker' to describe crackers; this irritates real hackers no end.
The basic difference is this: hackers build things, crackers break them.
If you want to be a hacker, keep reading. If you want to be a cracker, go read the alt.2600 newsgroup and get ready to do five to ten in the slammer after finding out you aren't as smart as you think you are. And that's all I'm going to say about crackers.
The Hacker Attitude Hackers solve problems and build things, and they believe in freedom and voluntary mutual help. To be accepted as a hacker, you have to behave as though you have this kind of attitude yourself. And to behave as though you have the attitude, you have to really believe the attitude. But if you think of cultivating hacker attitudes as just a way to gain acceptance in the culture, you'll miss the point. Becoming the kind of person who believes these things is important for you -- for helping you learn and keeping you motivated. As with all creative arts, the most effective way to become a master is to imitate the mind-set of masters -- not just intellectually but emotionally as well.
So, if you want to be a hacker, repeat the following things until you believe them:
1. The world is full of fascinating problems waiting to be solved. Being a hacker is lots of fun, but it's a kind of fun that takes lots of effort. The effort takes motivation. Successful athletes get their motivation from a kind of physical delight in making their bodies perform, in pushing themselves past their own physical limits. Similarly, to be a hacker you have to get a basic thrill from solving problems, sharpening your skills, and exercising your intelligence. If you aren't the kind of person that feels this way naturally, you'll need to become one in order to make it as a hacker. Otherwise you'll find your hacking energy is sapped by distractions like sex, money, and social approval.
(You also have to develop a kind of faith in your own learning capacity -- a belief that even though you may not know all of what you need to solve a problem, if you tackle just a piece of it and learn from that, you'll learn enough to solve the next piece -- and so on, until you're done.)
2. Nobody should ever have to solve a problem twice. Creative brains are a valuable, limited resource. They shouldn't be wasted on re-inventing the wheel when there are so many fascinating new problems waiting out there. To behave like a hacker, you have to believe that the thinking time of other hackers is precious -- so much so that it's almost a moral duty for you to share information, solve problems and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones.
(You don't have to believe that you're obligated to give all your creative product away, though the hackers that do are the ones that get most respect from other hackers. It's consistent with hacker values to sell enough of it to keep you in food and rent and computers. It's consistent to use your hacking skills to support a family or even get rich, as long as you don't forget you're a hacker while you're doing it.)
3. Boredom and drudgery are evil. Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do -- solve new problems. This wastefulness hurts everybody. Therefore boredom and drudgery are not just unpleasant but actually evil. To behave like a hacker, you have to believe this enough to want to automate away the boring bits as much as possible, not just for yourself but for everybody else (especially other hackers).
(There is one apparent exception to this. Hackers will sometimes do things that may seem repetitive or boring to an observer as a mind-clearing exercise, or in order to acquire a skill or have some particular kind of experience you can't have otherwise. But this is by choice -- nobody who can think should ever be forced into boredom.)
4. Freedom is good. Hackers are naturally anti-authoritarian. Anyone who can give you orders can stop you from solving whatever problem you're being fascinated by -- and, given the way authoritarian minds work, will generally find some appallingly stupid reason to do so. So the authoritarian attitude has to be fought wherever you find it, lest it smother you and other hackers. (This isn't the same as fighting all authority. Children need to be guided and criminals restrained. A hacker may agree to accept some kinds of authority in order to get something he wants more than the time he spends following orders. But that's a limited, conscious bargain; the kind of personal surrender authoritarians want is not on offer.)
Authoritarians thrive on censorship and secrecy. And they distrust voluntary cooperation and information-sharing -- they only like `cooperation' that they control. So to behave like a hacker, you have to develop an instinctive hostility to censorship, secrecy, and the use of force or deception to compel responsible adults. And you have to be willing to act on that belief.
5. Attitude is no substitute for competence. To be a hacker, you have to develop some of these attitudes. But copping an attitude alone won't make you a hacker, any more than it will make you a champion athlete or a rock star. Becoming a hacker will take intelligence, practice, dedication, and hard work. Therefore, you have to learn to distrust attitude and respect competence of every kind. Hackers won't let posers waste their time, but they worship competence -- especially competence at hacking, but competence at anything is good. Competence at demanding skills that few can master is especially good, and competence at demanding skills that involve mental acuteness, craft, and concentration is best.
If you revere competence, you'll enjoy developing it in yourself -- the hard work and dedication will become a kind of intense play rather than drudgery. And that's vital to becoming a hacker.
Basic Hacking Skills The hacker attitude is vital, but skills are even more vital. Attitude is no substitute for competence, and there's a certain basic toolkit of skills which you have to have before any hacker will dream of calling you one. This toolkit changes slowly over time as technology creates new skills and makes old ones obsolete. For example, it used to include programming in machine language, and didn't until recently involve HTML. But right now it pretty clearly includes the following:
1. Learn how to program. This, of course, is the fundamental hacking skill. If you don't know any computer languages, I recommend starting with Python. It is cleanly designed, well documented, and relatively kind to beginners. Despite being a good first language, it is not just a toy; it is very powerful and flexible and well suited for large projects. But be aware that you won't reach the skill level of a hacker or even merely a programmer if you only know one language -- you need to learn how to think about programming problems in a general way, independent of any one language. To be a real hacker, you need to have gotten to the point where you can learn a new language in days by relating what's in the manual to what you already know. This means you should learn several very different languages.
If you get into serious programming, you will have to learn C, the core language of Unix (though it's not the one to try learning first thing). Other languages of particular importance to hackers include Perl and LISP. Perl is worth learning for practical reasons; it's very widely used for active web pages and system administration, so that even if you never write Perl you should learn to read it. LISP is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days, even if you never actually use LISP itself a lot.
It's best, actually, to learn all four of these (Python, C, Perl, and LISP). Besides being the most important hacking languages, they represent very different approaches to programming, and each will educate you in valuable ways.
I can't give complete instructions on how to learn to program here -- it's a complex skill. But I can tell you that books and courses won't do it (many, maybe most of the best hackers are self-taught). What will do it is (a) reading code and (b) writing code.
Learning to program is like learning to write good natural language. The best way to do it is to read some stuff written by masters of the form, write some things yourself, read a lot more, write a little more, read a lot more, write some more ... and repeat until your writing begins to develop the kind of strength and economy you see in your models.
Finding good code to read used to be hard, because there were few large programs available in source for fledgeling hackers to read and tinker with. This has changed dramatically; open-source software, programming tools, and operating systems (all built by hackers) are now widely available. Which brings me neatly to our next topic...
2. Get one of the open-source Unixes and learn to use and run it. I'm assuming you have a personal computer or can get access to one (these kids today have it so easy :-)). The single most important step any newbie can take towards acquiring hacker skills is to get a copy of Linux or one of the BSD-Unixes, install it on a personal machine, and run it. Yes, there are other operating systems in the world besides Unix. But they're distributed in binary -- you can't read the code, and you can't modify it. Trying to learn to hack on a DOS or Windows machine or under MacOS is like trying to learn to dance while wearing a body cast.
Besides, Unix is the operating system of the Internet. While you can learn to use the Internet without knowing Unix, you can't be an Internet hacker without understanding it. For this reason, the hacker culture today is pretty strongly Unix-centered. (This wasn't always true, and some old-time hackers aren't happy about it, but the symbiosis between Unix and the Internet has become strong enough that even Microsoft's muscle doesn't seem able to seriously dent it.)
So, bring up a Unix -- I like Linux myself but there are other ways (and yes, you can run both Linux and DOS/Windows on the same machine). Learn it. Run it. Tinker with it. Talk to the Internet with it. Read the code. Modify the code. You'll get better programming tools (including C, Lisp, Python, and Perl) than any Microsoft operating system can dream of, you'll have fun, and you'll soak up more knowledge than you realize you're learning until you look back on it as a master hacker.
For more about learning Unix, see The Loginataka.
To get your hands on a Linux, see the Where can I get Linux.
3. Learn how to use the World Wide Web and write HTML. Most of the things the hacker culture has built do their work out of sight, helping run factories and offices and universities without any obvious impact on how non-hackers live. The Web is the one big exception, the huge shiny hacker toy that even politicians admit is changing the world. For this reason alone (and a lot of other good ones as well) you need to learn how to work the Web. This doesn't just mean learning how to drive a browser (anyone can do that), but learning how to write HTML, the Web's markup language. If you don't know how to program, writing HTML will teach you some mental habits that will help you learn. So build a home page.
But just having a home page isn't anywhere near good enough to make you a hacker. The Web is full of home pages. Most of them are pointless, zero-content sludge -- very snazzy-looking sludge, mind you, but sludge all the same (for more on this see The HTML Hell Page).
To be worthwhile, your page must have content -- it must be interesting and/or useful to other hackers. And that brings us to the next topic...
Status in the Hacker Culture Like most cultures without a money economy, hackerdom runs on reputation. You're trying to solve interesting problems, but how interesting they are, and whether your solutions are really good, is something that only your technical peers or superiors are normally equipped to judge. Accordingly, when you play the hacker game, you learn to keep score primarily by what other hackers think of your skill (this is why you aren't really a hacker until other hackers consistently call you one). This fact is obscured by the image of hacking as solitary work; also by a hacker-cultural taboo (now gradually decaying but still potent) against admitting that ego or external validation are involved in one's motivation at all.
Specifically, hackerdom is what anthropologists call a gift culture. You gain status and reputation in it not by dominating other people, nor by being beautiful, nor by having things other people want, but rather by giving things away. Specifically, by giving away your time, your creativity, and the results of your skill.
There are basically five kinds of things you can do to be respected by hackers:
1. Write open-source software. The first (the most central and most traditional) is to write programs that other hackers think are fun or useful, and give the program sources to the whole hacker culture to use. (We used to call these works ``free software'', but this confused too many people who weren't sure exactly what ``free'' was supposed to mean. Many of us now prefer the term ``open-source'' software).
Hackerdom's most revered demigods are people who have written large, capable programs that met a widespread need and given them away, so that now everyone uses them.
2. Help test and debug open-source software They also serve who stand and debug open-source software. In this imperfect world, we will inevitably spend most of our software development time in the debugging phase. That's why any open-source author who's thinking will tell you that good beta-testers (who know how to describe symptoms clearly, localize problems well, can tolerate bugs in a quickie release, and are willing to apply a few simple diagnostic routines) are worth their weight in rubies. Even one of these can make the difference between a debugging phase that's a protracted, exhausting nightmare and one that's merely a salutary nuisance. If you're a newbie, try to find a program under development that you're interested in and be a good beta-tester. There's a natural progression from helping test programs to helping debug them to helping modify them. You'll learn a lot this way, and generate good karma with people who will help you later on.
3. Publish useful information.(like me !) Another good thing is to collect and filter useful and interesting information into Web pages or documents like FAQs (Frequently Asked Questions lists), and make those generally available. Maintainers of major technical FAQs get almost as much respect as open-source authors.
4. Help keep the infrastructure working. The hacker culture (and the engineering development of the Internet, for that matter) is run by volunteers. There's a lot of necessary but unglamorous work that needs done to keep it going -- administering mailing lists, moderating newsgroups, maintaining large software archive sites, developing RFCs and other technical standards. People who do this sort of thing well get a lot of respect, because everybody knows these jobs are huge time sinks and not as much fun as playing with code. Doing them shows dedication.
5. Serve the hacker culture itself. Finally, you can serve and propagate the culture itself (by, for example, writing an accurate primer on how to become a hacker :-)). This is not something you'll be positioned to do until you've been around for while and become well-known for one of the first four things. The hacker culture doesn't have leaders, exactly, but it does have culture heroes and tribal elders and historians and spokespeople. When you've been in the trenches long enough, you may grow into one of these. Beware: hackers distrust blatant ego in their tribal elders, so visibly reaching for this kind of fame is dangerous. Rather than striving for it, you have to sort of position yourself so it drops in your lap, and then be modest and gracious about your status.
The Hacker/Nerd Connection Contrary to popular myth, you don't have to be a nerd to be a hacker. It does help, however, and many hackers are in fact nerds. Being a social outcast helps you stay concentrated on the really important things, like thinking and hacking. For this reason, many hackers have adopted the label `nerd' and even use the harsher term `geek' as a badge of pride -- it's a way of declaring their independence from normal social expectations. See The Geek Page for extensive discussion.
If you can manage to concentrate enough on hacking to be good at it and still have a life, that's fine. This is a lot easier today than it was when I was a newbie in the 1970s; mainstream culture is much friendlier to techno-nerds now. There are even growing numbers of people who realize that hackers are often high-quality lover and spouse material. For more on this, see Girl's Guide to Geek Guys.
If you're attracted to hacking because you don't have a life, that's OK too -- at least you won't have trouble concentrating. Maybe you'll get one later.
Points For Style
Again, to be a hacker, you have to enter the hacker mindset. There are some things you can do when you're not at a computer that seem to help. They're not substitutes for hacking (nothing is) but many hackers do them, and feel that they connect in some basic way with the essence of hacking.
Read science fiction. Go to science fiction conventions (a good way to meet hackers and proto-hackers). Study Zen, and/or take up martial arts. (The mental discipline seems similar in important ways.) Develop an analytical ear for music. Learn to appreciate peculiar kinds of music. Learn to play some musical instrument well, or how to sing. Develop your appreciation of puns and wordplay. Learn to write your native language well. (A surprising number of hackers, including all the best ones I know of, are able writers.) The more of these things you already do, the more likely it is that you are natural hacker material. Why these things in particular is not completely clear, but they're connected with a mix of left- and right-brain skills that seems to be important (hackers need to be able to both reason logically and step outside the apparent logic of a problem at a moment's notice). Finally, a few things not to do.
Don't use a silly, grandiose user ID or screen name. Don't get in flame wars on Usenet (or anywhere else). Don't call yourself a `cyberpunk', and don't waste your time on anybody who does. Don't post or email writing that's full of spelling errors and bad grammar. The only reputation you'll make doing any of these things is as a twit. Hackers have long memories -- it could take you years to live it down enough to be accepted.
Yet an other google hack! a hack for fun and totally harm less! just by entering a simple search string you can hack (intrude!) all the unprotected security webcams without being recognised(dat's wat i say as harmless ) jus type the given string here and start viewing..
What on earth is hacking? who is a hacker? what is hacking? now a days its very much heard about hacking!! lets see something about these wierd things , and i think this post should be dedicated to this sort of stuff..!
Hacker: nowadays this is a very powerfull tag, used by a lot of people that may be or not be a hacker.{:--))} By definition, Hacking is Gaining access to restricted areas by exploitation of errors or other means. is this right? Doing that makes me hacker?
Not quite.
Hacking is a lifestyle a living(i guess no wrong), and this starts sounding as a clich? but Hacking is really a lifestyle(quite intresting). A hacker is a person that analyzes troubles and find solutions in the most wild places, that any normal person could just skip. Hackers are curious, they always are looking for different approaches to problems and numerous solutions;
hackers are interested into learning new approaches and different ways to bring up solutions. A hacker is hungry for knowledge(yummie), wants to know how the simplest detail in a process works, and what and how would taking out that variable out would affect the entire process. Hackers are people interested in learning,(what makes sense if i use intuding?) and applying every concept they deal with. A hacker will never be a person that uses "tools" (exploits,virus,trojens..) and just simple click(or double click!) and point stuff to gain access to any system(intruding thats wat we love to do!!), thats a script kiddie, a hacker is a person worried about how that "tool" works and how can he/she(or they) make one. A hacker understands knwoledge and hunts it.
Hackers decide what to do with the knowledge, they may be destructive, which in my opinion is a bad decision, or they could be constructive(ethical), a helper, ethical. (even tho anyone is "bad" at times). And my aim is to put every bit and byte i know in this related field(me to a learner!)that makes me to share what all the info i have! be'coz i believe knowledge remains incomplete if it is not shared. keep visiting to see some cool(hmm hot) stuff which i collected from various means ...
Regedit: You may be thinking "Regedit, what the hell is that?!" or if you have a reasonable amount of experience with computers "Oh awesome a page about what this program is.
What is Regedit?
Regedit is basically a program that lets you edit ceratin values in your computer (short for "Registry Editor").
BEWARE, DON'T JUST PLAY AROUND IN REGEDIT, SOME THINGS CAN SERIOUSLY HARM YOUR COMPUTER IF CHANGED OR REMOVED.
You can do really cool things with it such as remove buttons on your computer .e.g remove the shutdown option or make a message appear at startup.
Before you do anything you will need to know how to access the program.: So first go to your start menu Then click run Now type "regedit" without the quotes Regedit should open (if it doesnt contact me)
How to display a legal notice on startup This is how to make a legal notice appear on startup:
Open Regedit
Navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system
legalnoticecaption:"enter your notice caption here"
legalnoticetext:"enter your legal notice text here"
Using Google, and some finely crafted searches we can find a lot of interesting information.
For Example we can find:
Passwords Software / MP3's ...... (and on and on and on) Presented below is just a sample of interesting searches that we can send to google to obtain info that some people might not want us having.. After you get a taste using some of these, try your own crafted searches to find info that you would be interested in.
Try a few of these searches: intitle:"Index of" passwords modified allinurl:auth_user_file.txt "access denied for user" "using password" "A syntax error has occurred" filetype:ihtml allinurl: admin mdb "ORA-00921: unexpected end of SQL command" inurl:passlist.txt "Index of /backup" "Chatologica MetaSearch" "stack tracking:"
Amex Numbers: 300000000000000..399999999999999 MC Numbers: 5178000000000000..5178999999999999 visa 4356000000000000..4356999999999999 "parent directory " /appz/ -xxx -html -htm -php -shtml -opendivx -md5 -md5sums"parent directory " DVDRip -xxx -html -htm -php -shtml -opendivx -md5 -md5sums"parent directory "Xvid -xxx -html -htm -php -shtml -opendivx -md5 -md5sums"parent directory " Gamez -xxx -html -htm -php -shtml -opendivx -md5 -md5sums"parent directory " MP3 -xxx -html -htm -php -shtml -opendivx -md5 -md5sums"parent directory " Name of Singer or album -xxx -html -htm -php -shtml -opendivx -md5 -md5sums Notice that I am only changing the word after the parent directory, change it to what you want and you will get a lot of stuff. METHOD 2: put this string in google search:?intitle:index.of? mp3You only need add the name of the song/artist/singer. Example: ?intitle:index.of? mp3 jackson METHOD 3:put this string in google search: inurl:microsoft filetype:iso You can change the string to watever you want, ex. microsoft to adobe, iso to zip etc… "# -FrontPage-" inurl:service.pwd Frontpage passwords.. very nice clean search results listing !!
"AutoCreate=TRUE password=*" This searches the password for "Website Access Analyzer", a Japanese software that creates webstatistics. For those who can read Japanese, check out the author's site at: coara
"http://*:*@www" domainname This is a query to get inline passwords from search engines (not just Google), you must type in the query followed with the the domain name without the .com or .net
"sets mode: +k" This search reveals channel keys (passwords) on IRC as revealed from IRC chat logs.
allinurl: admin mdb Not all of these pages are administrator's access databases containing usernames, passwords and other sensitive information, but many are!
allinurl:auth_user_file.txt DCForum's password file. This file gives a list of (crackable) passwords, usernames and email addresses for DCForum and for DCShop (a shopping cart program(!!!). Some lists are bigger than others, all are fun, and all belong to googledorks. =)
intitle:"Index of" config.php This search brings up sites with "config.php" files. To skip the technical discussion, this configuration file contains both a username and a password for an SQL database. Most sites with forums run a PHP message base. This file gives you the keys to that forum, including FULL ADMIN access to the database.
eggdrop filetype:user user These are eggdrop config files. Avoiding a full-blown descussion about eggdrops and IRC bots, suffice it to say that this file contains usernames and passwords for IRC users.
intitle:index.of.etc This search gets you access to the etc directory, where many many many types of password files can be found. This link is not as reliable, but crawling etc directories can be really fun!
filetype:bak inurl:"htaccess|passwd|shadow|htusers" This will search for backup files (*.bak) created by some editors or even by the administrator himself (before activating a new version). Every attacker knows that changing the extenstion of a file on a webserver can have ugly consequences. Let's pretend you need a serial number for windows xp pro.In the google search bar type in just like this - "Windows XP Professional" 94FBRthe key is the 94FBR code.. it was included with many MS Office registration codes so this will help you dramatically reduce the amount of 'fake' porn sites that trick you.or if you want to find the serial for winzip 8.1 - "Winzip 8.1" 94FBR
:Disclaimer :
You are responsible for what you do with this trick. Tech nerd is not held responsible for any damage caused by carelessness etc. yet to be posted ..! cheq often
Batch file hacking is very fun oh yeaa in this page we'll see some tricks and about them.
What Is A Batch File? A batch file is a MS-DOS file that will execute certain commands these files are usually made with notepad, Alot of people think batch files are nooby but if you know what your doing they can actually be quite powerful and by powerful i mean deleting a whole C:/ Drive.
Whats CMD? Ok Now you know what a Batch File is you need to know what CMD is ok well cmd is basicly MS-DOS it is a program that allows you to execute certain commands, CMD is simply short for Command Prompt which is its full name.
How To Get CMD?
Ok now were getting somewhere here are some simple ways to create and run cmd 1.Start>Run>"Type Cmd" and viola (If That Dosent Work Try Typing cmd.exe) 2.Notepad>(type command)>Save to desktop as (anything.bat) just make sure it has the extension (.bat) open it and theres C Prompt. 3.Right click anywhere on your desktop>New>shortcut>(type command)>enter>and on your desktop is C prompt. 4. Simply Go Start>Accesories>Command prompt. Lol 5. Go To C:\WINDOWS\system32\cmd
Tricks And Tips Ok you now know the basics of your hacking journey, here are some tricks that you can use.
1. Shutdown Error Ok this is a trick , when you click on this icon your about to make it will shut the computer down in the amount of time you set lets say 1min and you can leave a message, our message will be "You Got Owned".
To make this 1. Open Notepad, 2.Type Shutdown -s -t 60 -c "You Got Owned" 3. Save To Desktop As shutdown.bat (DONT FORGET THE .BAT) 4.You will now have an icon on yor desktop thats called shutdown.bat 5. Double click on it to execute and an error message will come up saying "Shutdown Will Commence In 1min" and below that will be a message saying you got owned. Thank You That Is My First Trick.
2.Shutdown Another Computer (Must Know IP Or Computer name. Ok this trick is the same as the one above, but! it will shutdown someone over a network, (they must be online) alright it is very similar to the one above just do this.
1. Open Notepad. 2. Type, shutdown -s -m \\ (IP Or Computer Name) 3. Save To Desktop As Shutdown.bat (AGAIN DONT FORGET .BAT!) 4.You wil now have an icon on your desktop call shutdown.bat 5.Double click to execute it and there computer should shutdown =D
Google has some fantastic potential for you to find whatever you are after on the internet.
To search for a book / program / file perhaps try the following.
Go to Google's search page and use the following criteria in the search dialog
intitle:index.of? file extension Name of item
e.g. intitle:index.of? chm syngress
This will hopefully give you a listing of all websites that google has cached that contain references to files in CHM format that are published by SYNGRESS.
How are servers hacked? Its an age old question passed around by the people who have never done this before. The hacking of servers isnt easy, to some people it is, and to some people the script kiddies and the newbies prehaps would think its hard due to the fact that they dont know anything about it. Lets get started on this tutorial.
When planning to hack a server, you need to use your intelligence. Gathering information is a key factor to this task. Why must you gather information? Because information is always needed especially when its server information. But what type of information on the server is needed? Well lets take a look deeper inside.
There a various ways of gathering information on servers such as Banner Grabbing. For those who dont know wat a banner is, it is the message echoed back to a remote connector to a server. For an example of a banner grabbing situation read below:
The example above was me using telnet to connect to a remote server on port 80 (HTTP) to get the HTTPD banner of the server. But what does this tell us? This can tell us a lot such as...
- the server runs apache 1.3.27 - the server runs linux - the server runs php 4.3.3 RC2-dev - the server runs frontpage 5.0.2.2 - the server runs OpenSSL 0.9.6b - the server uses chunked transfer-encoding
Well this is alot. but some are asking, it says unix though, how do you know theyre running linux? Well this is where the intelligence comes in, not everyone would take the guess of stating the remote operating system of the server without the use of a fingerprinting tool, but grabbing the http banner kinda gives it away. If it says Unix, majority of the time its some sort of Linux distro, which one? it does say so you dont know, sometimes when i would attack a server that only said linux and did id;uname -a in their shell, it would say GNU Linux, but that was only one server. Most other servers will say their operating system in the HTTP banner, such as Linux-RedHat so right there you would see it was redhat linux.
Other questions such as "Where do people find the exploits to hack these servers??" can also be answered. Majority of people will visit security sites and exploit websites to find these exploits either because they themselves dont know how to code, or they dont have any "connections" or friends with the newest exploits aka 0day's.
How else do people find exploits... Well lets take a look even deeper in how this is done. Say for example you want to attack some server thats running FreeBSD, you know theyre running it because you used some fingerprinting tool or a remote operating system detector and know it. Yet you want to find some sort of way you could exploit something on this server, how would you do this? A lot of people can usually easily do this, How? Well what many script kiddies and newbies dont do that the real hackers do is actually Read advisories first rather than go straight for the exploits thinking that they can just hack about anything. Why are advisories important though... they dont show you how to exploit. Yes, thats true but your ahead of the game seeing what exploits plan on coming. The advisories are always there before the exploits unless some coder apparently finds this exploit first making it the 0day he'll give to few people being invisible to the world. But... reading an advisory, how does this help at all. Lets say for example your on packetstormsecurity.nl, you made the choice to look over the top 10 advisories rather than the top 10 exploits, you notice theres one advisory for FreeBSD, you take a look at it. Remember... you dont know what version of FreeBSD this server is running... If you do then thats great but lets continue on as if you didnt know, But you can still tell what version of FreeBSD they would be running if you look at their server statistics for example heres some code from a FreeBSD exploit:
What does this tell us? Well lets see... If you do a banner grab on the FreeBSD server to get the http banner, you'll see for an example Server: Apache 1.3.24. How would that help? Take a look at the exploit code for all the FreeBSD versions with Apache 1.3.24, you will notice that only two of them have its, FreeBSD 4.4 and FreeBSD 4.5. Apparently you would say to yourself its either, most likely the newer version, but this method isnt always right, a hacker isnt always right, its learning from your mistakes that make you wiser, testing and testing over and over again, and luck has nothing to do with it. Anyway back to advisories... You notice that you see an advisory for FreeBSD, you look deeper into the advisory and notice that FreeBSD 4.4 systems are affected to say for example a CVS exploit that you can cause a buffer overflow in giving write access and possible remote command execution, Now remember, its just an advisory, But how can you impliment it? Theres the part where many people get stuck, thats why its best when you code your own exploits. Right here is the part where im sure i shouldnt go on because its the part where a lot of people get stuck but i will say this, Hackers or Coders would impliment this advisory by creating a 0day or just an exploit that happens to create the buffer overflow and i dunno, probably bind shell or port and let you in or just remote command execution. Thats why nowadays its a good thing to start learning to code c and c++, and even perl. Learn shellcode, learn to understand what shellcode is, and how to create your first exploit, and understand what all the commands are telling the server to do for a further understanding of even how every other exploit works and their process to give people access, learning is a key in hacking.
For all those people who wish to trace the people on the internet here is a cool good working site. The process being very simple.
* First you should register in the site with you mail address. * They will give a personalised url address for you. * All you have to do is share the url with the victim and some make him to open it. * Thats it, his details would be logged down. * You will recive a mail regarding the details of the victim. * The details include his IP address,ISP,Operating System,Browser,Country,City,Langitude,Latitude and many more details.
This is a very good service. I was using this services for a long time. The service was really good and I used to trace the persons whom i used to meet online.
How cool is that? It's really cool! You can send special messages in recorded audio that no one would even guess to your friend in picture format. It's like combining 2 files to become 1 and when you run the combined file, it will by default display the picture. To listen to the audio that is embedded into the picture file, you'll need to manually load the combined file into Winamp. Here's the test I did.
1. Combine audio (.mp3) with picture (.gif) I use the command "copy picture.gif /b + audio.mp3 /b combined.gif" in DOS prompt.
I look in my C: drive and now I have a new file "combined.gif" I run the combined.gif file and it display the same picture as picture.gif. I run Winamp and manually load the combined.gif, I am able to play the audio.mp3 sound. I tried to load combined.gif file into Windows Media Player and I can only see the picture.gif. No sound at all. Looks like Winamp can support this feature but not Windows Media Player.
2. Combine audio (.wav) with picture (.gif) I use the same picture.gif but now I am combining the picture file with a .wav sound file. Wav is another type of sound format. Used the same command "copy picture.gif /b + audio.wav /b combined.gif" in DOS prompt. I ran combined.gif and it is able to display the picture.gif picture file. Tried to load it into Winamp, doesn't play this time. Loaded the combined.gif into Windows Media Player, it also only display the picture but no sound. Looks like only .mp3 sound format is supported.
3. Combine audio (.mp3) with picture (.jpg) Since only mp3 works, we'll try combining mp3 with another type of picture format with is JPG. Used the same command "copy picture.jpg /b + audio.mp3 /b combined.jpg" in DOS prompt. Ran the combined.jpg and it displayed the picture.jpg. Then I tried loading the combined.jpg into Winamp, and it played the music. Again, loaded combined.jpg into Windows Media Player, I can only see the picture but no music.
From the test above, I believe that hiding audio inside picture can only work when you embed MP3 audio into picture file. I also believe that other picture format such as TIFF, PNG or Bitmap will work. Tom Scott explains that the GIF format allows for an "application extension block" - an arbitrary section for applications that isn't checked by the GIF parser. Meanwhile, Winamp and other MP3 players ignore all data in the file that isn't marked as an MP3 block. The result: the picture viewer ignores the music, and the MP3 player ignores the picture. Eventhough he only mentioned GIF, but I tested on JPG and it works as well.
If you're on a Linux box, you can do it by using the command "cat picture.gif sound.mp3 > combined.gif"
Software License details of Microsoft Office, Windows XP,Adobe Photoshop, Premiere, and tons of other software can easily be located on Google by running this simple query: "Belarc Advisor Current Profile" "Software Licenses" "Software Name" key: Copy the exact string in Google search bar and replace the Software name with the name of the software.
The only problem is that innocent users have placed these HTML reports in public directories of their web servers, the search engine spiders index them and in-turn expose the secret software keys to the whole world.
Though most new Adobe and Microsoft software will require additional web or phone activation, that is not mandatory if the Belarc reports have Volume License keys. Scary. ANYTHING CAN BE POSSIBLE WITH GOOGLE , JUS GOOGLE IT!
The biggest problem with tabbed user interface of Firefox browser is accidentally closing the tabs. Most of users close the tabs accidentally when they switch between them.
Luckily Firefox has a nice feature which provides solution to this problem. You can re-open the recently closed tabs by navigating through the menu-----> History-->Recently Closed Tabs.
Stop Firefox from Pre-Fetching Web Pages And Reduce Your Bandwidth
Firefox browser has a little bandwidth hungry feature which downloads the pages which it thinks you may view. When a webpage hints Firefox that certain pages are likely to be visited, it automatically downloads them so that they can be displayed immediately when the user requests.
For example when you search Google for iMac, Google Search results webpage hints browsers to pre-fetch http://www.apple.com/imac/ webpage.
If you are highly concerned about the bandwidth usage and resources (like CPU and Memory) you can stop Firefox from pre-fetching the pages.Follow these steps to stop Firefox pre-fetching the pages
Type about:config in the address bar Locate the configuration key network.prefetch-next (you can use filter to easily locate keys) Right click on the configuration key network.prefetch-next and select Toggle to change the value to false That's it done. From now onwards your Firefox browser will not download any pages unnecessarily
Spped up firefox
These are few steps to make your firefox run at lightining speed.
1. First in the URL bar, Type about:config. This will bring up a list of commands and variables you can edit.
2. The second step is to put network.http.pipelining in the filter and change the value to true.
3. After that you will want to put network.http.proxy.pipelining in the filter. Like the last one, make that value set to true also.
4. Next, locate network.http.pipelining.maxrequests and change the value to some number higher, say 10,20 or even 30, it would make up to 10,20 or 30 requests at once.
5. The last step is to right click anywhere and select New then Integer. Name it nglayout.initialpaint.delay and make its value "0″(make value ZeRo). This will make the browser respond faster on the information of the websites it receives.
Name:
|devilofdisguise| Home:Google |da land of live
thunders| About Me:
Never Explain Yourself-
your friends dont need it,
Your Enemies wont believe it
