Before U Hack (Basics)

BEFore U Hack


----------------------------------
Table of Contents:
----------------------------------
Before you start:

- What is an IP address?

- What is an ISP?

- What is a TCP/IP packet?

- How to spoof your IP

- How to use Telnet

- How to use HyperTerminal

- How to use Ping

- How to use TraceRoute

- How to use a proxy server



Stuff you'll need to know BEFORE you start:

-----------------------------------

What is an IP address?

IP stands for Internet Protocol, IP addresses are used by other computers to identify computers that connect to
them. This is how you can be banned from IRC, and how they can find your ISP. IP addresses are easily obtained, they
can be retrieved through the following methods:

-you go to a website, your IP is logged

-on IRC, anyone can get your IP

-on ICQ, people can get your IP, even if you have the option set "do not show ip"
they can still get it

-if you are connected to someone, they can type "systat", and see who is connected to them

-if someone sends you an email with IP-logging java, they can also get your IP address

There are many more ways of obtaining IP addresses, including using back-door programs such as Sub7 or NetBus.

------------------------------------

What is an ISP?

ISP stands for Internet Service Provider, they are the ones that give you the internet. You connect to one everytime
you dial-up and make a connection. People can find your ISP simply by running a traceroute on you (traceroute is
later explained). It will look something like this:

tracert 222.222.22.22

Tracing route to [221.223.24.54]
over a maximum of 30 hops.
1 147ms 122ms 132ms your.isp [222.222.22.21]
2 122ms 143ms 123ms isp.firewall [222.222.22.20]
3 156ms 142MS 122ms aol.com [207.22.44.33]
4 * * * Request timed out
5 101ms 102ms 133ms cisco.router [194.33.44.33]
6 233ms 143ms 102ms something.ip [111.11.11.11]
7 222ms 123ms 213ms netcom.com [122.11.21.21]
8 152ms 211ms 212ms blahblah.tts.net [121.21.21.33]
9 122ms 223ms 243ms altavista.34.com [121.22.32.43] <<< target's isp
10 101ms 122ms 132ms 221.223.24.54.altavista.34.com [221.223.24.54]
Trace complete.

-----------------------------------

What is a TCP/IP packet?

TCP/IP stands for Transmission Control Protocol and Internet Protocol, a TCP/IP packet is a block of data which is
compressed, then a header is put on it and it is sent to another computer. This is how ALL internet transfers occur,
by sending packets. The header in a packet contains the IP address of the one who originally sent the packet. You
can re-write a packet and make it seem like it came from anyone!! You can use this to gain access to lots of systems
and you will not get caught. You will need to be running Linux or have a program which will let you do this. This
tutorial does not tell you to use this on a Cisco router, but it does come in handy when hacking any system. If
something goes wrong when you try to hack a system, you can always try this...

------------------------------------

How to spoof your IP:

Find a program like Genius 2 or DC IS, which will let you run IdentD. This will let you change part of your
computer's identity at will! Use this when you get banned from some IRC chat room.... you can get right back in! You
can also use it when you are accessing another system, so it logs the wrong id...

------------------------------------

How to use telnet:

You can open telnet simply by going to your Start Menu, then to Run, and typing in "telnet".

Once you have opened telnet, you may want to change some features. Click on Terminal>Preferences. Here you can
change the buffer size, font, and other things. You can also turn on/off "local echo", if you turn local echo on,
your computer will show you everything you type, and the other computer you are connected to will show you aswell.
So you may get something like this;

You type "hello", and you get
hhelelollo

This is because the information has bounced back and got scrambled with what you typed. The only reason I would use
this is if the machine does NOT return what you are typing.

By default, telnet will connect to a system on the telnet port, which is port 23. Now you will not always want to
connect to port 23, so when you go to connect, you can change the port to maybe 25, which is the port for mail
servers. Or maybe port 21, for FTP. There are thousands of ports, so make sure you pick the right one!

----------------------------------

How to use HyperTerminal:

HyperTerminal allows you to open a "server" on any port of your computer to listen for incoming information from
specified computers. To use this, go to
Start>Programs>Accessories>Communications>HyperTerminal. First you will need to select the connection, pick "TCP/IP
Winsock", and then put in the computer to communicate with, and the port #. You can tell it to listen for input by
going to Call>Wait for Call. Now the other computer can connect to you on that port, and you can chat and transfer
files.

----------------------------------

How to use Ping:

Ping is easy, just open the MS-DOS prompt, and type "ping ip.address", by default it will ping 3 times, but you can
type

"ping ip.address -t"

Which will make it ping forever. To change the ping size do this:

"ping -l (size) ip.address"

What ping does is send a packet of data to a computer, then sees how long it takes to be returned, which determines
the computer's connection speed, and the time that it takes for a packet to go back and forth (this is called the
"trip time"). Ping can also be used to slow down or even crash a system if the system is overloaded by ping floods.
Windows 98 crashes after one minute of pingflooding (it's connections buffer is overflown - too many connections are
registered, and so Windows decides to take a little vacation).
A ping flood attack takes a lot of bandwidth from you, and you must have more bandwidth than your target (unless
the target is a Windows 98 box and you have an average modem, that way you'll knock it down after approximately a
single minute of ping flooding). Ping flooding isn't effective against stronger targets, unless you have quite a few
evil lines to yourself, and you have control over a few bandwidth-saavy hosts that can ping flood your target as
well.
Note: DOS's -t option doesn't do a ping flood, it just pings the target continously, with intervals from one ping to
another. In every Unix or Linux distribution, you can use ping -f to do a real pingflood. Actually ping -f is
required if you want your distribution to be POSIX-compliant (POSIX - Portable Operating System Interface based on
uniX), otherwise it's not a real Unix/Linux distribution, so if you have an OS that calls itself either Unix or
Linux, it has the -f switch.

----------------------------------

How to use TraceRoute:

To trace your connection (and see all the computer's between you and a target), just open the MS-DOS prompt, and
type "tracert ip.address" and you will see a list of computers, which are between you and the target computer.

You can use this to determine if there are firewalls blocking anything. And will also allow you to determine
someone's ISP (internet service provider).

To determine the ISP, simple look at the IP address before the last one, this should be one of the ISP's routers.

Basically, this is how traceroute works - a TCP/IP packet has a value in it's header (it's in the IP header. If you
don't know what this means, then ignore it and continue reading, it's not that crucial) called TTL, which stands
for Time To Live. Whenever a packet hops (travels through a router) it's TTL value is decreased by one. This is just
a countermeasure against the possibility that something would go wrong and a packet would ricochet all around the
net, thus wasting bandwidth.
So when a packet's TTL reaches zero, it dies and an ICMP error is sent back to the sender.
Now, traceroute first sends a packet with a TTL value of 1. The packet quickly returns, and by looking at the
sender's address in the ICMP error's header, the traceroute knows where the packet has been in it's first hop. Then
it sends a packet with a TTL value of 2, and it returns after the second hop, revealing it's identity. This goes on
until the packet reaches it's destination.

Now isn't that fun? :-)

----------------------------------

How to use a proxy server:

Do a search on the web for a proxy server which runs on the port of your choice. Once you find one, connect to it
with either telnet or hyperterminal and then connect to another computer through the proxy server. This way the
computer at the other end will not know your IP address.

----------------------------------

Section 1: why hack a cisco router?

You probably are wondering.. why hack into a cisco router?

The reason being is that they are useful when it comes to breaking into other systems...

Cisco routers are very fast, some with 18 T1 connections on one system, and they are very flexible and can be used
in DoS attacks or to hack other systems since most of them run telnet.

They also have thousands of packets going through them at any one time, which can be captured and decoded... A lot
of cisco routers are also trusted systems, and will let you have a certain amount of access to other computers on
it's network.

INTRODUCTION TO LINUX (hacking-machine)

1.0 - Intro

Linux- sometimes referred to by the press as 'Windows NT's worst enemy'.
Wired Magazine once called it 'The greatest story never told'. This is a
perfect definition because the story behind Linux is indeed a great one, yet
it is unknown to so many people. Let's start at the beginning.

Back when 'Stayin' Alive' was still topping the charts, and Microsoft was
a spec in the world of computers, AT&T produced a multi-user operating
system and labeled it 'UNIX'. Throughout the years, UNIX caught on and
many different versions of it began to come out. A popular one, called
'Minix' (mini-UNIX) was available for use at The University of Helsinki in
Finland. A student at the University named Linus Torvalds believed he
could create an operating system superior to Minix. In 1991 he started
his new operating system as a side project, but it soon developed into a
full-time hobby until 1994 when the first official version of the
operating system was released.

You're probably now saying 'so what's the big deal about Linux? Isn't it
just another operating system?' Absolutely not! First of all, Linux is
released under something called 'open source license'. Open source is really
more of an idea than a thing. Linux is released with all the source code and
files that it was made with. This means a few things. Anyone who is good
at programming can mess with the Linux code and release his own version of
it. This also means that even though if you buy Linux in a store it will
cost money, you're not paying for the actual Linux itself. Your money goes to
the price of packaging, the extra software that comes with the operating
system, and technical support. The second, and most important reason that
Linux is a big deal is because it's a much more stable operating system than
Windows. It runs on any system; even bottom of the line 386's from before
Linux even came out. Programs running under Linux almost never crash, and in
the off chance that one does because of bad programming by the program author,
it will not take the operating system down with it. Another important reason
Linux is good is that it is secure. It is much harder to bring down by a
hacker than Windows is (for further reading, read the 'Basic Unix Security
Guide' by R a v e N at blacksun.box.sk). This is just an extremely short list
of the reasons why Linux is so great. For further reading check out
www.linux.org

This tutorial is for Windows users who want to migrate to Linux. This is
written for Redhat or Mandrake Linux (the two most easy-to-install and
user-friendly Linux distributions), but the information here will most probably
help you with whatever distribution you are using. The only problem with this
is that Mandrake and RedHat are relativley simple to install, and some other
distrobutions are much more complex. I highly suggest you buy Linux-Mandrake
rather than RedHat. Mainly because it is cheaper and comes with more
software, but as you read through this tutorial, you'll see more reasons why I
recommend Mandrake.

The first thing you're going to have to do with your new operating system is
install it- but you can't do that so quickly.

2.0 - Preparation

If you already have Microsoft Windows on your system and you want it to
co-exist with Linux, you are going to have to create another hard drive
partition. What a hard drive partition is a totally separate part of a
hard drive. If two hard drive partitions weren't physically part of the
same disc, they would be two different hard drives. Anyway, the reason
for this is that Windows and Linux are totally different in the way they
access hard drives and handle files. If they are using each other's hard
drive space the two operating systems can conflict and cause major problems
for your computer. Well, as I was saying, you need to create a hard drive
partition reserved for Linux. There are MS-DOS programs that do this, but
they are "lethal" partition making programs. By this I mean that while making
a new partition, they can destroy or at least corrupt files on another
partition. If you want to make a partition for Linux, without killing your
Windows files you need a "non-lethal" partition program. If you get
Linux-Mandrake, a "non-lethal" partition program is included with it (this is
just one of the reasons why I recommend Mandrake over RedHat).

Well with all this talk of partitions and hard drives, you must be wondering
roughly how much hard drive space you'll need for Linux. If you want the
complete system with everything, you'll need about 1.5 gigabyte+ hard drive
space. However it is possible to productively run a full Linux distribution
(there are "miniature" Linux distributions that range from around 2 to 35
megabytes, and there's also Trinux, which runs from two 1.44MB floppy disks!
Get it from www.trinux.org) to with as little as 150 megabytes. Trust me, you
don't want EVERYTHING. Linux comes with tons of software you'll probably won't
need. For example: Linux comes with a variety of network servers - a web
server, a Sendmail server, a telnet server, an FTP server etc'. If you choose
not to install something and then regret, you can still get it later off the
original installation CD.

So anyway, if you have sufficient hard drive space, and a "non-lethal"
partition program, you're ready to proceed to the next step: installation.

***Even if you're using a "non-lethal" partition program, I suggest you
backup your Windows files just in case something goes wrong.***


3.0 - Installation

Now that your computer is ready for Linux, you're ready to install it.
When you bought the software, it probably came with a few CD's and a disk.

The disk is boot disk for the Linux installation program. You pop in the
disk, reset your computer, the installation program begins, and you're
ready to install Linux. The only thing is that the installation program
will take a while to load since it's from a disk.

**The stuff on the disk is probably just a duplicate of some of the stuff
on the first CD. If your computer is capable of booting from a CD (and
most newer ones are, otherwise, check your manual) then instead of putting
the disk in your computer then rebooting, put in the first CD as it will
load much quicker. Of course, you'll need to mess with your BIOS
configurations first, but that's no big deal. Hit del when your computer
boots up (after it tells you how much RAM you have) and mess around with it
until you can find out how to make your computer attempt to boot from your CD
drive first. This differs from different BIOS systems.**

3.1 - Ok..You're finally ready to install Linux.

The first few questions the install program asks you are self explanatory,
just things like your language and stuff. One thing you might get stumped
on is when you are prompted on whether you have any SCSI adapters or not.
An SCSI adapter can be anything such as a mouse, printer, scanner, etc. It
all depends if you have an SCSI controller. Chances are, you don't have any
SCSIs, but check your manual to be sure. Also, if you are completely sure
that your copy of Microsoft Windows is properly-configured, you can quit the
installation program at any time, return to Windows, run control panel, click
on system and find out all the information you'll need about your system's
hardware.

3.2 - More Partition Stuff

The next thing you might have trouble with is a dialog box that appears
asking you some questions about your hard drive partitions. The name of
the dialog box should 'Disk Setup'. There should be three buttons on the
bottom of the box. One labeled 'Disk Druid', another labeled 'fdisk', and
the last is the back button. Since you already set up your partitions,
select 'Disk Druid'. If you originally only had one partition with
windows, then the top of the screen should look something like this:

Mount Point Device Requested Actual Type
hda1 ??MB ??MB Win95
hda2 ??MB ??MB Linux Swap
hda3 ??MB ??MB Linux Native


Mount point should be blank.
'Device' is the name of the partition
'Requested' is the amount of hard drive space you wanted for the partition
'Actual' is the amount of hard drive space that is really in the partition
'Type' is what's in the partition


**The 'requested' and 'actual' sections for the 'Linux Swap" type should
be the amount of RAM you have.**

**It looks confusing, but in reality if it is simple. Don't worry if your
screen doesn't look exactly like my diagram, it probably won't.**

What you should do now is select the 'Linux Native' section (by pressing
tab to get to that part of the screen, then using the arrow keys) and then
press tab again until the 'edit' button is highlighted. Pressing spacebar
will bring up another dialog box. In the space provided, put a slash (/)
then press OK. Now you're back at the main screen. Press tab to get to
OK, and then press spacebar.

**what you're actually doing here is telling the computer to put the root
directory, signified by the slash, in the Linux Native partition. The
root directory '/', is similar to 'C:\' in DOS/Windows.**

Next you come to a screen asking which partitions to format. Select the
one that 'Linux Native' is in. You should select the '/dev/xxxx/'
partition where 'xxxx' is the name of the device that the Linux Native
partition is under. This is where you put the '/' on the last screen. If
the Linux Native partition device was hda3 then choose '/dev/hda3', if it
was hda6, then choose '/dev/hda6', you get the point.

**IT IS VERY IMPORTANT THAT YOU DO NOT SELECT THE WRONG PARTITION TO
FORMART!**


3.3 - Selecting What to Install

Suppose you had three hard drives on Windows - c:\, d:\ and e:\, and you
want to install Linux on d:\. Windows assigns the letter c to the first
hard drive it finds that has a DOS/Windows file partition, d to the second
DOS/Windows-compatible hard drive etc', so this might help you out
determining which device to choose. Also, if you turn d:\ into the Linux
hard drive, it will disappear from DOS/Windows, and e:\ will turn into
d:\.

You're not finished yet, but take a sigh of relief, the hardest part is
over. Next comes the screen asking which packages to install. Some of
the most important ones are selected already. If you have a lot of hard
drive space, select all the other packages. Otherwise, just select the
others that you think are important. Definitely select 'KDE' and 'GNOME'.
Those are window manager programs for the X-Windows system (a GUI - Graphical
User Interface), and we'll deal with them later. Anyway, newer versions always
come with new software and/or updates for old software.

Press OK and the Linux installation begins!

3.4 - Misc. Configurations

After everything has been installed, you are prompted for more things.
The first should be what resolution your monitor is. Most people would
like to use the same resolution they use on Windows, so if you don't know
which resolution you were using until now, switch back to Windows,
right-click on your desktop area, click properties and find the settings
tab. You should see your current resolution there. This would probably be
the same resolution you would want to use on Windows. If you want a higher
resolution, consult your monitor's manual to find out how high you can go.

Next is the mouse configuration. If your mouse is not on the list, select
'Generic PS/2 Mouse'.

There are more such as clock set and time zone but those are
self-explanatory. After this, comes the services screen. These are the
things that will startup when you run Linux. Then it will prompt you for
if you want the X-Windows interface to run when you start Linux. If you are a
Linux newbie (and you probably are, unless you weren't reading this guide), I
suggest you do this. X windows is the GUI system, as explained before.

The last configuration is the printer. This is self-explanatory.


3.5 - Configuring Users

Ok...you're almost done; the configurations are pretty much finished. Now
you will be prompted to create a password for the root operator. Even though
it is still very popular on single home users, Linux is a multi-user operating
system. Even if you'll be the only person using your computer, having a
multi-user system is quite benefical. For example: you can use a
less-privileged user to prevent yourself from doing stupid things and messing
things up. You can run sensitive software which can be broken to (say, some
sort of a server. For example: a Sendmail server for outgoing mail if you're
planning to let people sent mail from your machine, or a web server if you
want to serve a website off your computer) as a less-privileged user, so if
someone will manage to exploit some hole in this software, he will have very
limited privileges (up to what the program needs to run properly) and he won't
be able to do much, or nothing at all in most cases (he won't have read
access to password files, he won't have write access to the website's files
so he won't be able to alter them etc'). On any UNIX-based system (and there
are many) the main user is called 'root'. The root has supreme power over the
system and supreme power over all the other users. In fact, he has unlimited
power (unless he or another root-privileged user chooses to impose access
limits, but root-privileged users can always restore their rights to the
fullest).

My root password is a particularly simple one. Mainly because I am the
only one who uses Linux on my computer (and besides that I trust my own
family!) and that my Linux system is not connected to the Internet (so
hackers [or crackers I should say] would have no way to get into my
system). Make your password anything not to complicated that you'll
forget it, but something that is very hard to guess.

After you're done making a password for the root user, you're prompted to
create an unprivileged, or ordinary user account. You make the user name,
credentials, and password. It may seem pointless at first to create
another user- especially an unprivileged one if you are the only one who
is going to be using Linux. However there is a big advantage to it. As a
root user, you can do anything to the system, including seriously messing
it up. Nothing will stop you because you are root. An ordinary user
account is like security so if you mess up, the system will stop you.

3.6 - Booting Configurations

Next you are asked if you want to create a boot disk. I strongly recommend
this because it will put the Linux boot stuff on the disk, not your computer.
If you put the Linux boot stuff on a computer with windows, it may conflict
with the windows boot stuff in case you ever reinstall Windows (go to
blacksun.box.sk/byteme.html and read #18 for a good example).

The Linux 'boot stuff' I'm talking about is a program called 'LILO'.
That's short for 'Linux Loader'. Anyway LILO installs itself to the boot
sector of the computer. The problem is that Windows also installs stuff
to the boot sector. LILO can install over Windows and let you choose to
either boot up Linux or Windows whenever you start up your computer. If you
choose Windows, it'll use Windows' "boot stuff".

Anyway, in my opinion, when the install program asks you to create a boot
disk, click Ok, then follow the directions to create a boot disk. Oh yeah,
by the way, when you make a boot disk, it puts LILO on that disk. When it
asks you to install LILO, just press Skip (unless you want to install
LILO, which most users will).

Congratulations! You're done installing Linux! When the installation
program ends, take the installation boot disk out of the drive. If you
booted the installation from CD, don't forget to take that out too.


4.0 - Running Linux

I bet you're glad to finish that installation! Now you're finally ready
to run the system. If you decided to create a boot disk, insert that into
the disk drive. If you decided to install LILO, just sit tight for now.
Regardless of what you did, reset your computer. If you used LILO, you
will get a prompt to load Linux or Windows. If you used a boot disk, the
system will startup automatically.

After the system starts up, the will get prompted for a user name and
password. This will look different depending on how you configured it in
the installation. If you chose to start the X Windows GUI automatically,
the username and password screen will look like it does in Windows (well,
sort of. X-Windows is much cooler, unless you're using some lame version of
it or some lame window manager). If you chose not to load the X Windows
interface at startup (like most advanced users will), you'll be presented
with a text-based interface. The text-based interface (the command console)
is much faster than the graphical system, but this also means you cannot view
any graphics until you start X-Windows (this is a good time to mention that
most people just call it X). Anyway, you can always run a command console
from an X window (usually called an "XTerm", which stands for X Terminal).
Anyway, the login screen will look pretty much the same regardless of
whether you are using RedHat or Mandrake.

If you're wondering what to type in the username box, that's easy. Your
username is 'root' (remember?). The password is the one that you selected
at installation.


5.0 - Using Linux

5.1 - Intro To The Console

Even though you'll probably be able to do everything with ease using the X
Windows GUI, there is still some stuff you should know. First off, don't
rely on a GUI for everything! That is very important because you will
learn a lot by using the console. The console is more powerful and can do a
lot of things you would REALLY like if you'll just grab a good basic Unix book
and start learning. After you do, you'll find yourself often opening an XTerm
window to run some console commands which you cannot run from X. If you
selected to start the GUI interface when Linux loads up, there are still lots
of ways to get to the console.

The console prompt should look somewhat like this (if you're logged in as root):
[root@localhost.localdomian]#

The first part identifies who you are, and the '#' is the actual prompt.
Any almost and UNIX type system, the '#' means you are root. On non-root bash
consoles (BASH - Bourne Again Shell. BASH is the most popular text-based
shell. Confused? Don't worry, we'll get to that in a second) this will be
replaced with a $. Anyway, you can change the prompt, but we won't get into
that now.

5.11 - Shells

You use a shell everytime you're in the Linux console. What a shell is,
is the program that communicates between you and the Kernel (the kernel is
the core of the system). Let's think of it as an interpreter for for two
people who are trying to have a meeting, except they don't speak the same
language. One speaks English and the speaks, oh let's say Hebrew (about half
the members of Black Sun Research Facility (blacksun.box.sk if you don't
know the URL yet. Also, if you havn't noticed, I'm a member of BSRF) are from
Israel). To communicate with each other they need a guy who speaks both
English and Hebrew. If the English guy wants to tell the Hebrew guy
something, he tells it to the interpreter in English, and then the
interpreter tells it to the other guy in Hebrew, and vice versa. Well
anyway, getting back to the subject, this is the case with Linux. Your
language is the Linux commands, and the Kernel speaks it's own very complex
language. When you want to talk to the Kernel, you tell shell in your
language, and the shell tells it to the Kernel in it's language. On any Linux
system, there a few shells. Some of them are:

ash
bash
bsh
csh
tcsh
zsh

The most popular and powerful shell is 'bash' (borne again shell). We
won't go that much into shells, because you don't need to know that much
about them just yet.


5.2 - Navigating The File System

The most important thing to know when using the console is how to navigate
the file system without a graphical program.

The first thing to understand about this is that the bottom directory, the
directory that everything else is a subdirectory of is '/'. It's like
'C:\' in Windows.

Ok, you start at the console and as a default you're either in your home
directory (every user has a home directory which contains his personal
configurations files). Now you want to navigate to another directory. But
wait, you don't know any other directories! You'll a directory listing for
this, right? To do this type 'ls' at the prompt. 'ls' is the equivlant to
'dir' in MS-DOS, and stands for list. You'll get a list of files and
folders. To make the list a bit more readable, try ls -Fla. The -a shows
files which start with a period (for example: .Xclients-default). The -l
displays file permissions and displays everything in neat columns. The -F
option adds a / after a directory and a * after an executable file. I also
suggest using ls -Fla --color to let the system color-code different files
(may not be available on some systems).

Anyway, now that you what directories there are, you need to know how to
get into them. Luckily, you use the same command as you you use in
MS-DOS, the 'cd' (change directory) command. Let's say you're at the
bottom directory, '/' and you want to get to '/root'. You simply type
'cd root'. There is no need to type 'cd /root', because you're already in
'/'. Now let's say you want to get to '/root/bin'. This would be done by
typing 'cd bin'. There is no need to type 'cd /root/bin' (the "full path" of
the directory), since you're already in '/root'. Instead, you can use a
"relative path", which is a path that is relative to the current directory
you're in. Type pwd to find out where you are (pwd stands for print working
directory).

Now let's say you're in '/root/bin' and you want to get to '/usr'. You would
type 'cd /usr'. This is to signify that the 'usr' directory is under '/', not
'/root/bin', or even '/root'. Got it? Ok, just one more thing. If you're in
a subdirectory, and you want to get to the top directory, just type 'cd ..'.
Let's say you're in '/root/bin', and you want to get to '/root'. You could
just type 'cd /root', but hey, '/root' is five characters! If you want to
save precious miliseconds, just type 'cd ..', since '/root' is the directory
in which '/root/bin' is a subdirectory of. So in other words, . is the
current directory, .. is one directory above, ... is two directories above
etc'.

5.3 - Basic File and Directory Commands

There are lots of file and directory commands in Linux, but we'll start
with directory commands because they're easier. First off, you have
'mkdir'. 'mkdir' stands for make directory and the context is:

mkdir the_directory_you_want_to_make

Some rulse apply. If you're '/', it will make the new directory under
'/'. If you're in '/usr', it will make the directory under '/usr'. Of
course though, if you're in '/' and you want to make a directory called
'stuff' under '/usr', you would simply type '/usr/stuff'.

The next command is the 'rm' command. It works with files and direcotires
and is used to delete some, it stands for 'remove'. If you want to remove
a file called 'this.gif', you would go to the directory where that file is
and type 'rm this.gif'. Or let's say again you're in '/' and 'this.gif'
is in '/usr', you would type 'rm /usr/this.gif'. It works the same way
with a directory.

Next are the 'cp' and 'mv' commands. They're both relativley simple, but
we'll start with 'cp'. 'cp' stands for copy, and is used to copy a file
from directory to another. The context is:

cp /directory_where_it_is/filename /directory_where_you_want_to_copy_it

Of course if you're already in the directory where the file is, all you
need to type is:

cp filename /directory_where_you_want_to_copy_it

'mv' works the exact same way, except it moves the file instead of copying
it. This means it deletes in from the original directory and puts it in
the new one.


5.4 - Finding and Viewing Commands

To find a file, oyu use the 'find' command. It then followed by the
directory where you want to start looking, then the '-name' arguement to
say that you're searching for a filename. Next you type the name of the
file. Let's say you're looking for the 'this.gif' in the '/usr'
directory, the context would look like this:

find /usr -name this.gif

The find command doesn't stop at filenames, it can also search a file for
a paticular string of text. It has the same context as the find file
command except you put quotes and asteriks around the string of text. So
if you wanted to search the '/usr' directory for a file containing the
string 'hello', you would type

find /usr -name "*hello*"

Ok, once you find a file, you want to view it right? Well, you could open
the file with a text editor, but we haven't learned to use tetx editors
yet, and anyway if the file you want to view is important you might
accidently change it and save it using a text editor. That's what the
'cat' command is for. Let's say you want to view a file called
'stuff.txt' in '/root'. You would navigate to the '/root' directory and
type 'cat stuff.txt'. Or from any directory, type 'cat /root/stuff.txt'

-= For more commands, buy a good basic Unix book =-

5.5 - linuxconf

There are lots of commands in Linux for configuring everything to user
passwords, networks, and the message that comes up when you start Linux. With
so many things to configure, luckily there is one program that does it all.
Just type 'linuxconf' at the command prompt, and you'll be brought to the
Linux Configuration program.


5.6 - Mounting

5.61 - Mounting Drives

In Linux, drives not only have to be physically mounted to the computer, but
mounted in software too. In the KDE and GNOME GUIs, you can easily mount a
CD-ROM or disk drive by clicking on the 'CD-ROM' or 'Disk Drive' icons on the
desktop.

5.62 - How to mount

Remember earlier in this tutorial when we went over how a hard drive partition
is almost like a separate hard drive? Well, just like a separate drive,
partitions also have to be mounted. The main use in this is being able to
mount Windows partition and access Windows files in Linux. Obviously, Windows
software will not run under Linux but there is still a use for accessing
Windows files in Linux.

Let's say you can't use the internet in Linux. You ISP only allows to
dialup with software and they don't make it for Linux, you're not used to
Linux yet so you don't want to use the net in it yet. This is a down
point, but it doesn't mean you can't download Linux files to use. All you
have to do is download the files in Windows and access them in Linux.

To mount a windows partition in Linux, yhe first thing you must do is
create a directory in Linux where you will mount the windows partition to
reside. Go into file manager (it should be under utilities no matter what
distribution you're using) and create a new directory under '/'. Call
anything, I suggest calling it 'windows'. Now exit file manager and go
into 'terminal' (should also be under utilities). Terminal will give you a
command prompt just like MS-DOS. This is what you would have to do
everything from if there were no X Windows GUI. The command to use is
simply enough- 'mount'. But don't type it just yet, you need to give the
system more info. The full command is

mount -t vfat /dev/xxxx /yyyyyyy (yes there is a space between 'xxxx' and '/')

Or mount -t vfat32 /dev/xxxx /yyyyyyy in case this is a FAT32 partition.

Where 'yyyyyyy' is the directory you just created, and 'xxxx' is the device
name of the partition where Windows resides. It is usually hda1 or something.

There, now just go into file manager and click on the directory you created
and you will have all the files that are on your windows partition.

When you're done, don't forget to unmount the drive by typing:

umount /dev/xxxx /yyyyyyy

Each time you want to access your windows files, just mount the partition
(unless they're set for automount. Edit /etc/fstab, find the line that
represents your Windows partition and look for a place with says noauto. If
you find the word noauto, change it into defaults. If you don't, your
Windows partition will probably get automounted whenever you boot-up Linux).
When you're done with them, just unmount the partition.


5.7 - Runlevels

While Windows is booting, have you ever pressed the F8 key? Well, if you
have, you're probably familiar with a screen that pops up giving you a
list of ways you can load Windows. There's safe mode, command prompt,
step-by-step confirmation, etc. Linux has something just like that, and
they're called 'runlevels'. There are six runlevels in all, and some are
pretty much the same. A runlevel is a list of commands to load-up as soon
as you start up Linux (there's a mini-tutorial about runlevels at
blacksun.box.sk/byteme.html). Your default runlevel is probably 5. If you
configured the GUI to start up when you boot the system, and if your default
runlevel is 5, then that is the runlevel configured to boot the GUI when it
starts up...simple, right?

Well anyway, if you use linuxconf to change your default runlevel to 2 or
3 or something, then you change it so that the GUI won't start as soon as
the system boots....all without touching the actual runlevel. When you
want to change it back, just use linuxconf to set the default runlevel
back to 5.

Now let's say you only want to load it without the GUI coming up once.
Instead of having to change the configuration in linuxconf, and then
changing it back, you can load Linux into another runlevel. Suppose You
want to load runlevel 2...not for any paticular reason, just because it's
not configured to load the GUI when it boots up, and well, you like the
number 2. To do this, as soon LILO comes up (whether it's on your
computer, or your boot disk), you have the option to type something next
to 'boot:'. Just type 'linux x'. 'x' refers to the number of the
runlevel, in this case the number 2, so you type 'linux 2', and press
enter. This will load Linux without loading the GUI. When you restart
Linux, it will load the default runlevel again.



You are now officially a Linux user. Check out www.linuxlinks.com for
links to some great Linux sites. The best way to learn about Linux is by
messing around with it. In an hour of playing with Linux you can learn a
lot. If you want more interesting yet simple and easy-to-understand tutorials,
check out sighthansraj.blogspot.com

guide to hack

............GUIDE TO (mostly) HARMLESS HACKING.........PART-1...

___________________________________________________________


Beginners Series #1

So you want to be a harmless hacker?
____________________________________________________________


You mean you can hack without breaking the law?"

That was the voice of a high school freshman. He had me on the phone because
his father had just taken away his computer. His offense? Cracking into my
Internet account. The boy had hoped to impress me with how "kewl" he was.
But before I realized he had gotten in, a sysadmin at my ISP had spotted the
kid’s harmless explorations and had alerted the parents. Now the boy wanted
my help in getting back on line.

I told the kid that I sympathized with his father. What if the sysadmin and
I had been major grouches? This kid could have wound up in juvenile
detention. Now I don’t agree with putting harmless hackers in jail, and I
would never have testified against him. But that’s what some people do to
folks who go snooping in other people’s computer accounts -- even when the
culprit does no harm. This boy needs to learn how to keep out of trouble!

Hacking is the most exhilarating game on the planet. But it stops being fun
when you end up in a cell with a roommate named "Spike." But hacking doesn't
have to mean breaking laws. In this book we teach safe hacking so that you
don’t have to keep looking back over your shoulders for narcs and cops.

What we're talking about is hacking as a healthy recreation, and as a free
education that can qualify you to get a high paying job. In fact, many
network systems administrators, computer scientists and computer security
experts first learned their professions, not in some college program, but
from the hacker culture. And you may be surprised to discover that
ultimately the Internet is safeguarded not by law enforcement agencies, not
by giant corporations, but by a worldwide network of, yes, hackers.

You, too, can become one of us.

And -- hacking can be surprisingly easy. Heck, if I can do it, anyone can!

Regardless of why you want to be a hacker, it is definitely a way to have
fun, impress your friends, and get dates. If you are a female hacker you
become totally irresistible to men. Take my word for it!;^D

These Guides to (mostly) Harmless Hacking can be your gateway into this
world. After reading just a few of these Guides you will be able to pull off
stunts that will be legal, phun, and will impress the heck out of your friends.

These Guides can equip you to become one of the vigilantes that keeps the
Internet from being destroyed by bad guys. Especially spammers. Heh, heh,
heh. You can also learn how to keep the bad guys from messing with your
Internet account, email, and personal computer. You’ll learn not to be
frightened by silly hoaxes that pranksters use to keep the average Internet
user in a tizzy.

If you hang in with us through a year or so, you can learn enough and meet
the people on our email list and IRC channel who can help you to become
truly elite.

However, before you plunge into the hacker subculture, be prepared for that
hacker attitude. You have been warned.

So...welcome to the adventure of hacking!

WHAT DO I NEED IN ORDER TO HACK?

You may wonder whether hackers need expensive computer equipment and a shelf
full of technical manuals. The answer is NO! Hacking can be surprisingly
easy! Better yet, if you know how to search the Web, you can find almost any
computer information you need for free.

In fact, hacking is so easy that if you have an on-line service and know how
to send and read email, you can start hacking immediately. The GTMHH
Beginners’ Series #2 will show you where you can download special
hacker-friendly programs for Windows that are absolutely free. And we’ll
show you some easy hacker tricks you can use them for.

Now suppose you want to become an elite hacker? All you will really need is
an inexpensive "shell account" with an Internet Service Provider. In the
GTMHH Beginners’ Series #3 we will tell you how to get a shell account, log
on, and start playing the greatest game on Earth: Unix hacking! Then in
Vol.s I, II, and III of the GTMHH you can get into Unix hacking seriously.

You can even make it into the ranks of the Uberhackers without loading up on
expensive computer equipment. In Vol. II we introduce Linux, the free
hacker-friendly operating system. It will even run on a 386 PC with just 2
Mb RAM! Linux is so good that many Internet Service Providers use it to run
their systems.

In Vol. III we will also introduce Perl, the shell programming language
beloved of Uberhackers. We will even teach some seriously deadly hacker
"exploits" that run on Perl using Linux. OK, you could use most of these
exploits to do illegal things. But they are only illegal if you run them
against someone else’s computer without their permission. You can run any
program in this book on your own computer, or your (consenting) friend’s
computer -- if you dare! Hey, seriously, nothing in this book will actually
hurt your computer, unless you decide to trash it on purpose.

We will also open the gateway to an amazing underground where you can stay
on top of almost every discovery of computer security flaws. You can learn
how to either exploit them -- or defend your computer against them!

About the Guides to (mostly) Harmless Hacking

We have noticed that there are lots of books that glamorize hackers. To read
these books you would think that it takes many years of brilliant work to
become one. Of course we hackers love to perpetuate this myth because it
makes us look so incredibly kewl.

But how many books are out there that tell the beginner step by step how to
actually do this hacking stuph? None! Seriously, have you ever read _Secrets
of a Superhacker_ by The Knightmare (Loomponics, 1994) or _Forbidden Secrets
of the Legion of Doom Hackers_ by Salacious Crumb (St. Mahoun Books, 1994)?
They are full of vague and out of date stuph. Give me a break.

And if you get on one of the hacker news groups on the Internet and ask
people how to do stuph, some of them insult and make fun of you. OK, they
all make fun of you.

We see many hackers making a big deal of themselves and being mysterious and
refusing to help others learn how to hack. Why? Because they don't want you
to know the truth, which is that most of what they are doing is really very
simple!

Well, we thought about this. We, too, could enjoy the pleasure of insulting
people who ask us how to hack. Or we could get big egos by actually teaching
thousands of people how to hack. Muhahaha.

How to Use the Guides to (mostly) Harmless Hacking

If you know how to use a personal computer and are on the Internet, you
already know enough to start learning to be a hacker. You don't even need to
read every single Guide to (mostly) Harmless Hacking in order to become a
hacker.

You can count on anything in Volumes I, II and III being so easy that you
can jump in about anywhere and just follow instructions.

But if your plan is to become "elite," you will do better if you read all
the Guides, check out the many Web sites and newsgroups to which we will
point you, and find a mentor among the many talented hackers who post to our
Hackers forum or chat on our IRC server at http://www.infowar.com, and on
the Happy Hacker email list (email hacker@techbroker.com with message
“subscribe”).

If your goal is to become an Uberhacker, the Guides will end up being only
the first in a mountain of material that you will need to study. However, we
offer a study strategy that can aid you in your quest to reach the pinnacle
of hacking.

How to Not Get Busted

One slight problem with hacking is that if you step over the line, you can
go to jail. We will do our best to warn you when we describe hacks that
could get you into trouble with the law. But we are not attorneys or experts
on cyberlaw. In addition, every state and every country has its own laws.
And these laws keep on changing. So you have to use a little sense.

However, we have a Guide to (mostly) Harmless Hacking Computer Crime Law
Series to help you avoid some pitfalls.

But the best protection against getting busted is the Golden Rule. If you
are about to do something that you would not like to have done to you,
forget it. Do hacks that make the world a better place, or that are at least
fun and harmless, and you should be able to keep out of trouble.

So if you get an idea from the Guides to (mostly) Harmless Hacking that
helps you to do something malicious or destructive, it's your problem if you
end up being the next hacker behind bars. Hey, the law won't care if the
guy whose computer you trash was being a d***. It won't care that the giant
corporation whose database you filched shafted your best buddy once. They
will only care that you broke the law.

To some people it may sound like phun to become a national sensation in the
latest hysteria over Evil Genius hackers. But after the trial, when some
reader of these Guides ends up being the reluctant "girlfriend" of a convict
named Spike, how happy will his news clippings make him?

Conventions Used in the Guides

You've probably already noticed that we spell some words funny, like "kewl"
and "phun." These are hacker slang terms. Since we often communicate with
each other via email, most of our slang consists of ordinary words with
extraordinary spellings. For example, a hacker might spell "elite" as
"3l1t3," with 3's substituting for e's and 1's for i's. He or she may even
spell "elite" as "31337. The Guides sometimes use these slang spellings to
help you learn how to write email like a hacker.

Of course, the cute spelling stuph we use will go out of date fast. So we do
not guarantee that if you use this slang, people will read your email and
think, "Ohhh, you must be an Evil Genius! I'm sooo impressed!"

Take it from us, guys who need to keep on inventing new slang to prove they
are "k-rad 3l1t3" are often lusers and lamers. So if you don't want to use
any of the hacker slang of this book, that's OK by us. Most Uberhackers
don't use slang, either.

Who Are You?

We've made some assumptions about who you are and why you are reading these
Guides:

· You own a PC or Macintosh personal computer
· You are on-line with the Internet
· You have a sense of humor and adventure and want to express it by hacking
· Or -- you want to impress your friends and pick up chicks (or guys) by
making them think you are an Evil Genius

So, does this picture fit you? If so, OK, d00dz, start your computers. Are
you ready to hack?

_________________________________________________________
Want to see back issues of Guide to (mostly) Harmless Hacking? See either
http://www.vcalpha.com/silicon/void-f.html or
http://www3.ns.sympatico.ca/loukas.halo8/HappyHacker/
http://www.geocities.com/TimesSquare/Arcade/4594

We have a discussion group and archives hosted at
http://www.infowar.com/cgi-shl/login.exe.

Chat with us on the Happy Hacker IRC channel. If your browser can use Java,
just direct your browser to www.infowar.com, click on chat, and choose the
#hackers channel.

Subscribe to our email list by emailing to hacker@techbroker.com with
message "subscribe"

Want to share some kewl stuph with the Happy Hacker list? Correct mistakes?
Send your messages to hacker@techbroker.com. To send me confidential email
(please, no discussions of illegal activities) use carolyn@techbroker.com
and be sure to state in your message that you want me to keep this
confidential. If you wish your message posted anonymously, please say so!
Direct flames to dev/null@techbroker.com. Happy hacking!
Copyright 1997 Carolyn P. Meinel. You may forward or post on your Web site
this GUIDE TO (mostly) HARMLESS HACKING as long as you leave this notice at
the end..
________________________________________________________

The Newbies Guide to Hacking and Phreaking
-by Sight Hansraj
NOTICE: TO ALL CONCERNED Certain text files and messages contained on this site deal with activities and devices which would be in violation of various Federal, State, and local laws if actually carried out or constructed. The webmasters of this site do not advocate the breaking of any law. Our text files and message bases are for informational purposes only. We recommend that you contact your local law enforcement officials before undertaking any project based upon any information obtained from this or any other web site. We do not guarantee that any of the information contained on this system is correct, workable, or factual. We are not responsible for, nor do we assume any liability for, damages resulting from the use of any information on this site.

The Newbies Guide to Hacking and Phreaking

By: Sight Hansraj
v1.0
E-Mail: sighthansraj@gmail.com
*This document was made for educational purposes only, so if you use it and get caught for* *some stupid reason, its your own fault.*

Note: This file will not make you a hacker. This is only a reference

Chapters

The Introduction

The Understandment
1.1 What is hacking?
1.2 Why do we hack?
1.3 What are the most important things about a hacker?

The Introduction into the hacking world
2.1 Finding a mentor
2.2 Friends
2.3 Hacking groups
2.4 IRC

The start of your hacking experience
3.1 Reading text
3.2 Telnet
3.3 Phreaking
3.4 UNIX
3.5 Social Engineering
3.6 Programming
3.7 Cracking
3.8 Trial -n- Error

Closing

Introduction

This guide is made only for educational purposes people. If you get busted because of this text file, hey, its yer fault. Not mine. I made this to expand the minds of those that are clueless. For the people on AOL that wanna get out of the lame AOL soil, for the people who are clueless in the hacking world, for those who want to expand their minds, for those who care about exploring! Do me a favor since I wrote this all for you people, don't abuse or alter this text please!

.....Cyber-fox......

So, we begin with the Newbies Guide to Hacking and Phreaking.................

Chapter 1- The Understandment

1.1 What is hacking?

Hacking is not going into a system and destroying files and just ........ up some guys computer up. Hacking is going into AOL chat rooms and TOS'ing some kids ass. Hacking is not going into the IRC advertising and showing off what script or bot yer using. Hacking is not emailbombing, using programs, winnuking someone, using ICMP attacks on someone, or saying that you are a hacker. Hacking is intruding a system and exploring the host's computer and getting whatever information you need and getting yourself out and clearing your trails without getting yourself busted. It's all for knowledge. "Knowledge is freedom, freedom is knowledge."

1.2 Why do we hack?

Why do we hack? We all have different reasons. My reason is to explore, find the secrets of the government, show the host of a server their problems and to help newbies out as best as I can. People can hack because they want to do the same thing as I want to do, or to just show off their "skillz", or to get popular, or to gain friends, or even to get a girlfriend (what a pathetic reason.). Anyways, we all hack for different reasons. That's that.

1.3 What are the most important things about a hacker?

The most important things about a hacker? We all have different opinions but for a newbie, don't take shit from other people. That's my advice. If some idiot or other hacker comes up to you and starts .....in around with you, just ignore them. If you want, just use an ICMP attack on them so that their Winbloze95 system freezes up. However, I'd just keep out of it and ignore them. If you want to be a hacker, the main thing is to read. Read all the mother.....in text files that you can get your hands on!

There are more but I'll list them at the bottom. Enough of this section. Go out there and read!

Also, get a shell if yer a newbie. Get a .....in UNIX shell. Go do a websearch on your local ISP and buy one. Don't try to hack one because you'll be stupid enough to get caught trying to break in. heh.

Chapter 2 - The Introduction into the hacking world

2.1 Finding a Mentor

I wouldn't exactly find a mentor. I don't like being that type of hacker. But that's optional. If you find a mentor, his responsibility is to help you out in as many ways that he can. However, don't expect that you'll become a hacker faster if you have a mentor. There is no shortcut or faster way of becoming a hacker. Sooner or later, you'll have to do some shit on your own. To find a mentor, I would go onto some hacking digests or e-zines and write a request for a mentor, or teacher, or go on the web looking for someone. If you go to a "really cool" website, don't just ask! Get to know some people and find out how much of a hacker they are.

2.2 Friends

Friends in the hacking world are the most important thing that I can think of. Friends support you, friends care about you, friends help you with your hacking problems, friends get in touch with you, and most of all, friends don't decieve or fool around with you. The first thing you should do is go and find some friends. Check some H/P/C sites out and get to know them. Go to your local 2600 conference and meet some friends. Friends are the key. I don't think anything else is more important. Without friends, you'll get no where. Believe me.

2.3 Hacking groups

I dunno about you, but I would join a hacking group. One that you know is stable and that have reliable and good friends. Ask around, search the web. If you don't find any, make one. Go to your local 2600 conference and get some friends, then make a group. If that doesn't work, email me and I'll help you out. Again, there is no shortcut to hacking so don't expect to become a hacker faster. The point of hacking groups is to have a bunch of friends working together, to protect each other, to gain respect from each other and to share knowledge.

2.4 IRC (Internet Relay Chat)

Ahhh, the IRC. The IRC is a tool to help you grow your knowledge. I used to go to #hackphreak on the Undernet till I got booted by NetJammr. Revelation introduced me to this channel. Anyways, there are a lot of hacking channels on the IRC to help you out. #hack, #hacking, #hackers, #2600, etc. Get an IRC client first. If you have Winbloze95, get mIRC. If you have Linux, get BitchX, or ircii. I don't really like the IRC too much because most of the people there are assholes and jerks, but hopefully you can find some reliable and cool guy to help you out. Don't beg for ops, don't act like a jerk, just be cool and act nice and you'll get your reward.

Chapter 3 - The start of your hacking experience

3.1 Reading text

Ok, for you kids out there reading this, the best way to become a hacker is to read text files like this. Text files are the ultimate key to becoming a hacker, I think. Correct me if I'm wrong but I don't think that you can become a hacker without reading some reading material that's related to hacking. I don't believe in "teaching" hacking because that just means yer too lazy and complacent to do shit yourself. Instead, yer not working as hard as the person who's teaching the shit to you (whatever that means.) I don't read a lot so maybe that's why I'm not such a great hacker but I'm telling you, whenever I do read something, I know %100 more than what I knew before. Reading is such a great thing to newbies. Just read, read and read some more. Then when yer done with the text, read it again and again. Yer never the perfect hacker. There's always new things to be explored and to be unlocked.

3.2 Telnet

Telnet is an application that lets you to communicate and connect to another server such as: nyct.net. Telnet is one of the most useful things that I can think of. It lets you go from one place to another. A lot of people hack using telnet. I hack using telnet most of the time. When you telnet, you go into other O/S's such as, UNIX, Linux, FreeBSD, OpenBSD, VAX/VMS, etc. Also, there are various ports that let you connect to different parts of the server such as SMTP (sendmail (simple mail transfer protocol) port for UNIX. Usually port: 25) Port 23 connects you to the login prompt. There are numberous ports in one system. One way to get a track into a port is to get a port scanner. From then, you can get into an open port, run an exploit, and get your way through. I recommend CRT for a telnet program for those newbies that run Windows95.

3.3 Phreaking

Phreaking is a cool thing. For those that don't know what it is, its just fondling with the phone system. I don't know much about it but I can tell you about some of the boxes that are used such as the Red Box, the Green Box, Black Box, etc. Many boxes such as the Blue Box do not work anymore. The Red Box generates these 5 cent, 10 cent, and 25 cent tones. What you do, is go to a local payphone (one that does'nt have AT&T or Nynex on it) and take the phone off the hook and just simply press the cent tones. You make free phone calls this way. Also, you can make a profit outta this too! What you can do, is ask the operator to make a long distance phone call for you, then just put in the tones for the amount needed, then hang up after the call is completed. Then call the operator back and say that it did'nt go through and that you want your money back. You will be sent a check or cash to your home the next couple of days. I don't know if this really works or not because I almost got busted by a cop and ran away. For a newbie, the Red Box is "the" box to start off, I think because its so easy to use.

To make a red box, simply get a tone dialer at Radio Shack, then buy a crystal from someone at your local 2600 displayed: 6.50 or 6.55536. I prefer the 6.50. Correct me if I'm wrong but different areas in the country need different crystals to work out the Red Box. I will get into other boxes in the next version but for now, use the Red Box.

3.4 UNIX

UNIX is my amigo (friend for all of you dumbasses out there!) I have a distribution of UNIX that is called Linux, made by Linus Traverold. There are other distributions such as, IRIX, BSD, XENIX, HP/UX, DG/UX (Digital Unix), etc. I can go on forever. I really recommend getting a Linux Distribution such as Redhat, or Slackware. Slackware would be my choice. Get the latest version with the latest Kernel, then get a book called: "Linux in a Nutshell." It tells you different commands for Linux. Also, make sure you don't have a .....in winmodem for Linux because if you do, yer stuck! I'm really recommending you to get Linux if you want to get into UNIX hacking. Then when you mastered Linux, get into BSD or something else.

3.5 Social Engineering

Ahhhhh, Social Engineering. I'm just too young to do it, but I love it. Social Engineering is when you con someone to giving you their login and password for a system. A good example of this is in the fake ass movie, "Hackers." In the beginning, Dade Murphy calls up a TV station worker who is stupid enough to give the TV station server number out. Dade Murphy cons his way to getting it using his fast thinking abilities. Social Engineering can be done in many different ways such as, using the camera trick, over the phone, using email, fax, etc. The camera trick was taught to me by my close friend/mentor, Bernz. I learned that if you go to local companies and go to a secretary, you can easily get a login/password by saying that you want to record some info on the company. She'll probably give you a tour or something, I dunno, for a little while. Then ask her if you can see the computer and stuff. From what I heard, secretaries love to show off their "skillz" on computers, but they don't know a .....in thing about who's stealin who's logins/passwords. That's when you roll the tape on record and get all the information you need to login. For more on Social Engineering, go view Bernz's Social Engineering FAQ.

3.6 Programming

Programming is important to your hacking career. You cannot become a hacker without learning how to code. When you code, you make the program do what you want it to do, you tell it what to do and how you want to do it. You can make various programs such as crackers, exploits, scripts, etc. Programming is very, very important. If you don't know any programming languages, go buy a book on C, C++, or Perl. Learn any program language but I recommend those any of those 3. After you have learned Linux or UNIX, make your programs, test them and BANG, you made your first program.

3.7 Cracking

Sometimes Social Engineering does'nt always work, so there's always another option. Cracking. On Linux or UNIX systems rather, you can get the .passwd file and crack it. There are many methods of cracking. A good text/book on this is Orc's Guide to Cracking. However, I will explain some methods of cracking. One way of cracking is to get the .passwd file from the server, then using a cracking program, but most of the time, its shadowed. That's why I prefer Social Engineering but then again, its less trouble.

Another way is to use a packet sniffer. When you get linux, get linsniff.c, then compile it and run it. It works great. Packet Sniffers take a certain amount of packets that come from the server so the password of some user can come through and get caught by the person who's sniffing it. A way to prevent this from happening to you is to get SSH (Secure Shell.)

I don't know much about cracking so get Orc's Guide to Cracking or get the GTMHH (Guide to Mostly Harmless Hacking) on cracking. I learned how to crack mostly through that specific file. You can get it from Silicon Toads site (http://www.silitoad.org) or TACD (http://www.tacd.org.)


3.9 Trial -n- Error

Trial -n- Error is the way of the hacker. This is how hackers do it. They try one thing, then try another. If you try one thing, its not always certain to work out. Don't get fustrated if you screw up once because hey, it's hard to hack. No one ever said it was easy! Hacking is really a tool. We're vandalists. We make marks on peoples lives. We do illegal things because we explore. Trial -n- Error is the only way you can succeed in hacking. That's the truth! It's not an opinion! Maybe you'll hack your server on the first try but it'll probably be luck. You can't always do it on the first try. Its trial -n- error. Do one thing, and if it does'nt work, hell try another.

Closing

Well, that's about it for this version. If you have any comments or questions, please email: sighthansraj@gmail.com I'll try to help you as best as I can. If you think my grammar sucks, deal with it because I hate english vocab. and all that shit! When you email me, try to be to the point. Be as specific as you can. Until next time, take it easy people.

Cyber-fox
email: sighthansraj@gmail.com




To the best of our knowledge, the text on this page may be freely reproduced and distributed.
If you have any questions about this,mail me.....

"Hacking - Tutorial"

guys, Hacking is a game ,which will be fun if u want to play and learn not to harm any body ,so if u wana be hacker ,you must enjoy the "hacking".....
this is my first post of the being a "HACKER" tutorial
First-step: A perfect platform
If u want to be a hacker, you have to choose a platform which is suitable and that is linux cause its free ,widely supported community.....so choose "Backtrack"
which is highly made for pentesters"GET it from "www.backtrack-linux.org"
BACKTRACK,he highest rated and acclaimed Linux security distribution to date. BackTrack is a Linux-based penetration testing arsenal that aids security professionals in the ability to perform assessments in a purely native environment dedicated to hacking. Regardless if you’re making BackTrack your primary operating system, booting from a LiveDVD, or using your favorite thumbdrive, BackTrack has been customized down to every package, kernel configuration, script and patch solely for the purpose of the penetration tester.

BackTrack is intended for all audiences from the most savvy security professionals to early newcomers to the information security field. BackTrack promotes a quick and easy way to find and update the largest database of security tool collection to-date.

Our community of users range from skilled penetration testers in the information security field, government entities, information technology, security enthusiasts, and individuals new to the security community. Feedback from all industries and skill levels allows us to truly develop a solution that is tailored towards everyone and far exceeds anything ever developed both commercially and freely available.

Whether you’re hacking wireless, exploiting servers, performing a web application assessment, learning, or social-engineering a client, BackTrack is the one-stop-shop for all of your security needs.