User talk:Mukhtiarchachar

Hello, my name is Mukhtiyar Ali Chachar Im going to tell u about Computer Hacking

Hacking is a term that has often been used by the media to describe the various activities of certain computer users (in a poor way, sadly). The movie Hackers (movie) did a lot to influence the populace and the press this way. There are some fantastic books that help to explain what a real hacker is like:

Hackers, by Steven Levy The Devouring Fungus, by Karla Jennings Free as in Freedom, by Sam Williams Just for Fun, by Linus Torvalds The Cathedral and the Bazaar, by Eric Raymond This wikibook will also shed some light on hacking, and what hackers actually do (and who they actually are).

Hackers are people who tend to play around with their knowledge of computers to make things happen and generally have methods of getting around the systems which are not meant to be got around. First, the term hackers is explained. This is one of the most important chapters to read, for it will give you a insight of what hacking really is. Next, the history of computing and hackers is described. This might explain a couple of things suggested wrongly (maybe by accident) by the media. The 'hacking-culture' follows up next and 'finally' the real thing is assesed. (Note: These methods are illegal if used wrongly, yet the method to prevent or 'cure' this 'attack' is given as well to remain as objective as possible).

I would appreciate if anyone posts stuff which will help the world dealing with security and 'dealing' with hackers (mostly crackers and scriptkiddies).

The Jargon File or New Hackers dictionary defines the term hacker quite nicely, It also does an exceptional job of pointing out that one does not need to be affiliated with computers at all to be considered a hacker.

The excerpt from The Jargon File:

hacker: n. [originally, someone who makes furniture with an axe] 1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary. RFC1392, the Internet Users' Glossary, usefully amplifies this as: A person who delights in having an intimate understanding of the internal workings of a system, computers and computer networks in particular. 2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming. 3. A person capable of appreciating hack value. 4. A person who is good at programming quickly. 5. An expert at a particular program, or one who frequently does work using it or on it; as in ‘a Unix hacker’. (Definitions 1 through 5 are correlated, and people who fit them congregate.) 6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example. 7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations. 8. [deprecated] A malicious meddler who tries to discover sensitive information by poking around. Hence password hacker, network hacker. The correct term for this sense is cracker. [edit] A perspective view on hackers The first part of this book is intended for the reading of non-hackers in order to build an understanding of who hackers really are. Don't skip this part if you want to obtain an objective view on hacking. First of all, the definition of hackers is redefined, since a lot of commercial put it in a rather commercial perspective (so to say). Then, their history is covered. This 21 century hold many 'miracles', so hacking should be casted in the world of technology if people were to understand them. Yet the hacking-culture is covered in a seperate chapter. This is due the not-so simple way in which hackers tend to work. Finally, ethics, shared by most hackers are covered so that you know what hackers stand up for. link title

[edit] Terminology Hack is an onomatopoeic verb describing the noise and actions of chopping at something with a blade (i.e.: He hacked away at the underbrush with a machete), or a particularly nasty cough (i.e.: The chainsmoker hacked up some orange phlegm), but which also came to describe the act of typing on a typewriter, for the same reason (the annoying, incessant HACK HACK HACK, Ding! CRASH! HACK HACK HACK, &c). From there it became associated not only with the action itself, but also those doing the typing. For example, a "hack"--a bad writer/journalist--would "hack out" a poorly researched or unoriginal story on his typewriter. While the quieter tapping of computer keyboards began to replace the harsh noise of the typewriter, the old terminology was carried over to the new technology. Thus, the original "hackers," (long before the PC or word processors,) were merely called that because they would spend their days "hacking away" at their console keyboards, writing code. (It's worth noting that, when computing was in its infancy and console time at the giant mainframes was scarce, programmers would often hand-write code or type it out on typewriters before they manually plugged it into the machine. Also, the earliest consoles were basically automated typewriters.)

Nowadays, a hacker is, within the software development community, any skilled programmer, especially among open-source developers. A "hack," in turn, is a quick-and-dirty patch, fix, or utility which may not be well documented or necessarily reliable, but which gets the job done, whatever that job may be.

Crackers are skilled programmers who exploit the limitations of computer networks, and write up cracks--malicious hacks--to automate the dirty work. These hacks/cracks may attempt to break into remote machines (Ex: He hacked into the schools server to increase his phys-ed grade.), crack passwords (the most useful utility for this is simply called Crack), decrypt data, or simply modify proprietary software so the cracker doesn't have to pay for it(Ex: He downloaded a cracked version of Dreamweaver, because he couldn't afford to buy it.). Viruses, trojans, and worms are also hacks/cracks of a sort. Crackers are especially fond of worms, which spread without user interaction and can be used to create giant, distributed supercomputers that can then be used to attack other computers (the Code Red worm used the combined power of infected computers to flood the White House web server, making it inaccessible to regular users for a time). When a hacker finds a security hole in the software they're using, they hack out some code to patch it. When a cracker finds a hole, they hack out code to exploit it, ideally bringing remote computers under their control.

Script-kiddies use hacks and cracks created by real programmers, but they use their software without really understanding the code that's doing the work.

As indicated above, not all hacks are "malware" (malicious code). User-created shell scripts and batch files that automate tasks (like workstation startup, permission settings, data backup, &c.) are hacks, too. Hacks are tools (script-kiddies are tools too, but anyway). They are hacked out to make someone's life easier, but not necessarily yours.

TV news and, of course, the movie "Hackers" brought the label hacker to the attention of the wider public, but failed to acknowledge its broader meaning, instead using it as a buzzword, so as not to confuse the less informed members of their audience ("Computer programs are written by people? Like books? I thought other computers made them!"). Others have latched on to the grit, glamour, and rebellion the buzzword hacker invokes; thus, they think of hacking as something of a religion. But, in short, it's nothing more than playing around with computer code. You don't even need to be connected to the internets to do some hacking, just learn a programming language.

SELECT BIBLIOGRAPHY

MALWARE: Fighting Malicious Code, by Ed Skoudis; Prentice Hall, 2004 Note: This book is wonderful, but requires some technical experience. Maximum Linux Security, Second Edition, by Anonymous; Sams, 2001 Note: There's probably a newer version available, but this was my introduction to computer security. and resources listed above, esp. The Cathedral and the Bazaar

Fleshed out by the Mole of Production 04:19, 10 Feb 2005 (UTC)

needs links to definitions of words outside the scope of this mod needs other useful links as most people think a module called "Computer Hacking" should tell them about computer cracking, there should be some actual discussion, even instruction, to that end. there should also be instruction on hardening everyday PCs against remote attacks. [edit] A brief history of computing (with hackers) As long as there have been computers, people were there to 'hack' them. But this activity really hit the headlines when the internet arrived. Yet history teaches that this event wasn't an evil thing at all, hackers actually 'maintain' the internet as it should be. It is unimaginable for the computer/internet society to grow so large without people who were at the cutting edge of technology (hacking internet it's way up). Just imagine how it would be if there weren't any hackers... Most technology you use today would cease to exist. Ask yourself: Would your computer be this powerful if it wasn't put to the edge? Would software be as reliable as they look? Would there be a spiral of new cutting edge innovations?

You can answer all these questions by no. It might seem strange to think positive of hackers, but know that much is done on the edge of society (mostly not in the middle).

So, as it was going. Computers ....

[edit] The hacker-culture Advanced computer users describe themself as hackers; those who use their skills for malevolent purposes are termed "crackers". The term crackers is a term consisting of the meaning of both criminals and hackers (thus forming crackers)(Note: this sounds like bull. Crackers break things, in the sense of cracking the integrity of a computer system; and they work through cracks in security, like climbing through a crack in a wall; but their main act is breaking into computers for example by figuring out the root password, which is like cracking a safe at a bank.--the Mole of Production 04:35, 10 Feb 2005 (UTC)). This means that crackers break the law, yet this isn't enough to get indepth information about the hacker-culture.

In this chapter the main hacker-personalities will be described. In a rather unusual way: the media is used to get to know the real group. This means that you'll be able to understand that some of the people certainly not worth the name hacker...

[edit] The ethics of hacking This is an important chapter (to become) for everybody who wants to know where hackers get their hacking-identity. Their motives and far more important, their shared ethics.

[edit] The process of defending against hackers [edit] The System Administrator's resources [edit] Single user systems There are several simple ways to defend a system against malicious attack although the measures needed vary with the use of the system. A single user server being the easiest to secure. The most obvious method, which is applicable to almost all types of systems, is to only run the servers/daemons which you need. If you run a thousand and one different daemons just because they came with your distro, you have to keep them up to date. If you are only running 2 or 3 you can keep checking for updates confident you didn't forget about that tftp server you never actually use, for example. It should go without saying that you should keep these things up to date, the sooner you can patch/upgrade a vulnerability in a daemon or a remote vuln in the kernel, the less you will be vulnerable to attack.

[edit] Multiple user systems These are the only things needed to reasonably defend a single user system, however when you have many user accounts, even if you trust the people given them ( you can never \really\ trust a user like this but lets not be paranoid), there are extra security measures which need to be implemented. These include strict priviledges for users accounts and a good password policy. It is one thing for an attacker to find a vulnerability in a program, but if they are simply allowed to use a dangerous program with a compromised account you will be under much more risk. If you have a complicated system where files need sharing between users, remember that you can create a seperate group for these users and use the group permissions to allow the users access without allowing world period between changing passwords, a user will use very simple passwords or worse use a Post-it on their monitor.

[edit] Random tidbits of info Attackers often use something called root-kits which make it seem like there is nothing untoward running despite the fact that they have control of your system. They do this by replacing common system utilities with versions which don't report the whole truth; for example, a version of ps which doesn't display processes with "0wned" in their name. These are called root kits as you have to be root (or a similar all powerful user) to install these on a system, wikipedia covers root kits. You can defend against a root kit using a Intrusion Detection System (IDS); however if you suspect that something unpleasant is happening, you can check using a known clean version of the system utilities. These can be found conveniently bundled in a package called busybox which can be found at http://www.busybox.net/download.html.

In such cases it is also possible to create ahead of time statically linked versions of all of the utilites and to then write them to a CDROM that can be used in such situations.

However these days most common root-kits are kernel-based. Which means that root-kits infect (like a parasite) the core of the operating system where all basic operations are performed and where hardware is accessed. The operating system kernel manages process scheduling, memory management, device access and device drivers. When the kernel is infected by a root-kit (backdoor), for example like a device driver, through a loadable kernel module, there is no way to tell if a system is compromised because all input/output in the system can be faked. When the rootkit is in place memory usage, cpu usage, running processes and files and directories can all be hidden.

There is no remedy in this case in a running system. The only way to check a system's integrity in such cases is by booting the system from another read-only medium which is known to be trusted and to verify the integrity of the installed system through this means. It is possible to install integrity checking software such as tripwire or aide (advanced intrusion detection system) which builds a database of signatures of installed files. At a later point in time this database can be used to check if files have been changed and it is then possible to tell if a change was authorized or not.

Attackers could leave more than one means to get back in through the use of backdoors into the system so always make sure you removed all of them. If you have no database of signatures you are usually unable to be certain that you have found all backdoors and then it is recommended to reinstall the system to regain a known clean system

Mukhtiar_here@hotmail.com

Mukhtiar Ali Chachar
'''                       Hello SOme poets infront of u Duniya Se Jo Dare, Usse Kayar Kehte Hain, Duniya Jisse Dare, Usse Shayar Kehte Hain, Biwi Se Jo Dare, Usse Shohar Kehte Hain. - MARHAM Ek Be-wafa ke Zakham Pe Marham Lagane Hum Gaye Marham ki kasam, Marham na mila, Marham ki jagah Mar...hum...gaye..... - Aur bhi bahut si cheeze lut chu-ki hai dil ke saath Ye bataya dosto ne ishq farmane ke baad Is liye kamray ki ek ek cheez "ckeck" karta hoon main "Ek tere aane se pehle, ek tere jaa-ne ke baad" - Accha hua ke tum bewafa nikle Accha hua ke tum bewafa nikle.. Saale wafadaar to kutte hote hain - humne pyaar kiya bade josh ke saath humne pyaar kiya bade josh ke saath par ab pyaar karange badi soch ke saath kyunki kal unhe dekha kisi aur ke saath - Cigarette.. Zaalim tujhse tho yeh cigarette acchi hai Zaalim tujhse tho yeh cigarette acchi hai Dil ko jalaathi hai par hothon se lagi rahthi hai - Tum har raat Tum har raat mere khuwabon mein aao, Tum har raat mujhe yuunhi satao, Melody khao khud jaan jao. - * Mein tere pyar .......... Mein tere pyar mein paagal hua chhaliye, Mein tere pyar mein paagal hua chhaliye, Iodex maliye kaam pe chaliye - * Maine Tumshe Pyar Kiya... meine tuzhse pyar kiya par tere baap ne mujhe pita, tan ke shakti,maan ki shakti,bornvita. - kash ke tere chehre par chicken pox ke dhaag hote, chaand to tu hai he sitaare bhi saath hote. - Kamse kam maut se aisi mujhe ummid nahi thi Ai Jindgi tune to diya dhoke pe dhoka -'''
 * Yashomati maiyya Yashomati maiyya se puche Nandlala, Yashomati maiyya se puche Nandlala, Kya aaya naya ujala,char boondon wala? -
 * Before Marriage: Taqdeer hai magar kismat nahi khulti Tajmahal banana chahata hoon Lekin Mumtaz nahi milti *After Marriage: Taqdeer hai magar kismat nahi khulti Tajmahal banana chahata hoon Lekin Mumtaz nahi marti - *

Mukhtiar_here@hotmail.com