+++++++++++++++++++++++++++++++++++++++++++++++++

| the lod/h presents |

++++++++++++++++ ++++++++++++++++
\ a novice's guide to hacking- 1989 edition /
\ ========================================= /
\ by /
\ the mentor /
\ legion of doom/legion of hackers /
\ /
\ december, 1988 /
\ merry christmas everyone! /
\+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++/

**********************************************************************
| the author hereby grants permission to reproduce, redistribute, |
| or include this file in your g-file section, electronic or print |
| newletter, or any other form of transmission that you choose, as |
| long as it is kept intact and whole, with no ommissions, delet- |
| ions, or changes. (c) the mentor- phoenix project productions |
| 1988,1989 xxx/xxx-xxxx |
**********************************************************************

introduction: the state of the hack

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
after surveying a rather large g-file collection, my attention was drawn to
the fact that there hasn't been a good introductory file written for absolute
beginners since back when mark tabas was cranking them out (and almost
*everyone* was a beginner!) the arts of hacking and phreaking have changed
radically since that time, and as the 90's approach, the hack/phreak community
has recovered from the summer '87 busts (just like it recovered from the fall
'85 busts, and like it will always recover from attempts to shut it down), and
the progressive media (from reality hackers magazine to william gibson and
bruce sterling's cyberpunk fables of hackerdom) is starting to take notice
of us for the first time in recent years in a positive light.
unfortunately, it has also gotten more dangerous since the early 80's.
phone cops have more resources, more awareness, and more intelligence that they
exhibited in the past. it is becoming more and more difficult to survive as
a hacker long enough to become skilled in the art. to this end this file
is dedicated . if it can help someone get started, and help them survive
to discover new systems and new information, it will have served it's purpose,
and served as a partial repayment to all the people who helped me out when i
was a beginner.

contents
~~~~~~~~
this file will be divided into four parts:
part 1: what is hacking, a hacker's code of ethics, basic hacking safety
part 2: packet switching networks: telenet- how it works, how to use it,
outdials, network servers, private pads
part 3: identifying a computer, how to hack in, operating system
defaults
part 4: conclusion- final thoughts, books to read, boards to call,
acknowledgements

part one: the basics

~~~~~~~~~~~~~~~~~~~~
as long as there have been computers, there have been hackers. in the 50's
at the massachusets institute of technology (mit), students devoted much time
and energy to ingenious exploration of the computers. rules and the law were
disregarded in their pursuit for the 'hack'. just as they were enthralled with
their pursuit of information, so are we. the thrill of the hack is not in
breaking the law, it's in the pursuit and capture of knowledge.
to this end, let me contribute my suggestions for guidelines to follow to
ensure that not only you stay out of trouble, but you pursue your craft without
damaging the computers you hack into or the companies who own them.

i. do not intentionally damage *any* system.

ii. do not alter any system files other than ones needed to ensure your
escape from detection and your future access (trojan horses, altering
logs, and the like are all necessary to your survival for as long as
possible.)
iii. do not leave your (or anyone else's) real name, real handle, or real
phone number on any system that you access illegally. they *can* and
will track you down from your handle!
iv. be careful who you share information with. feds are getting trickier.
generally, if you don't know their voice phone number, name, and
occupation or haven't spoken with them voice on non-info trading
conversations, be wary.
v. do not leave your real phone number to anyone you don't know. this
includes logging on boards, no matter how k-rad they seem. if you
don't know the sysop, leave a note telling some trustworthy people
that will validate you.
vi. do not hack government computers. yes, there are government systems
that are safe to hack, but they are few and far between. and the
government has inifitely more time and resources to track you down than
a company who has to make a profit and justify expenses.
vii. don't use codes unless there is *no* way around it (you don't have a
local telenet or tymnet outdial and can't connect to anything 800...)
you use codes long enough, you will get caught. period.
viii. don't be afraid to be paranoid. remember, you *are* breaking the law.
it doesn't hurt to store everything encrypted on your hard disk, or
keep your notes buried in the backyard or in the trunk of your car.
you may feel a little funny, but you'll feel a lot funnier when you
when you meet bruno, your transvestite cellmate who axed his family to
death.
ix. watch what you post on boards. most of the really great hackers in the
country post *nothing* about the system they're currently working
except in the broadest sense (i'm working on a unix, or a cosmos, or
something generic. not "i'm hacking into general electric's voice mail
system" or something inane and revealing like that.)
x. don't be afraid to ask questions. that's what more experienced hackers
are for. don't expect *everything* you ask to be answered, though.
there are some things (lmos, for instance) that a begining hacker
shouldn't mess with. you'll either get caught, or screw it up for
others, or both.
xi. finally, you have to actually hack. you can hang out on boards all you
want, and you can read all the text files in the world, but until you
actually start doing it, you'll never know what it's all about. there's
no thrill quite the same as getting into your first system (well, ok,
i can think of a couple of bigger thrills, but you get the picture.)

one of the safest places to start your hacking career is on a computer

system belonging to a college. university computers have notoriously lax
security, and are more used to hackers, as every college computer depart-
ment has one or two, so are less likely to press charges if you should
be detected. but the odds of them detecting you and having the personel to
committ to tracking you down are slim as long as you aren't destructive.
if you are already a college student, this is ideal, as you can legally
explore your computer system to your heart's desire, then go out and look
for similar systems that you can penetrate with confidence, as you're already
familar with them.
so if you just want to get your feet wet, call your local college. many of
them will provide accounts for local residents at a nominal (under $20) charge.
finally, if you get caught, stay quiet until you get a lawyer. don't vol-
unteer any information, no matter what kind of 'deals' they offer you.
nothing is binding unless you make the deal through your lawyer, so you might
as well shut up and wait.

part two: networks

~~~~~~~~~~~~~~~~~~
the best place to begin hacking (other than a college) is on one of the
bigger networks such as telenet. why? first, there is a wide variety of
computers to choose from, from small micro-vaxen to huge crays. second, the
networks are fairly well documented. it's easier to find someone who can help
you with a problem off of telenet than it is to find assistance concerning your
local college computer or high school machine. third, the networks are safer.
because of the enormous number of calls that are fielded every day by the big
networks, it is not financially practical to keep track of where every call and
connection are made from. it is also very easy to disguise your location using
the network, which makes your hobby much more secure.
telenet has more computers hooked to it than any other system in the world
once you consider that from telenet you have access to tymnet, itapac, janet,
datapac, sbdn, pandanet, thenet, and a whole host of other networks, all of
which you can connect to from your terminal.
the first step that you need to take is to identify your local dialup port.
this is done by dialing 1-800-424-9494 (1200 7e1) and connecting. it will
spout some garbage at you and then you'll get a prompt saying 'terminal='.
this is your terminal type. if you have vt100 emulation, type it in now. or
just hit return and it will default to dumb terminal mode.
you'll now get a prompt that looks like a @. from here, type @c mail <cr>
and then it will ask for a username. enter 'phones' for the username. when it
asks for a password, enter 'phones' again. from this point, it is menu
driven. use this to locate your local dialup, and call it back locally. if
you don't have a local dialup, then use whatever means you wish to connect to
one long distance (more on this later.)
when you call your local dialup, you will once again go through the
terminal= stuff, and once again you'll be presented with a @. this prompt lets
you know you are connected to a telenet pad. pad stands for either packet
assembler/disassembler (if you talk to an engineer), or public access device
(if you talk to telenet's marketing people.) the first description is more
correct.
telenet works by taking the data you enter in on the pad you dialed into,
bundling it into a 128 byte chunk (normally... this can be changed), and then
transmitting it at speeds ranging from 9600 to 19,200 baud to another pad, who
then takes the data and hands it down to whatever computer or system it's
connected to. basically, the pad allows two computers that have different baud
rates or communication protocols to communicate with each other over a long
distance. sometimes you'll notice a time lag in the remote machines response.
this is called pad delay, and is to be expected when you're sending data
through several different links.
what do you do with this pad? you use it to connect to remote computer
systems by typing 'c' for connect and then the network user address (nua) of
the system you want to go to.
an nua takes the form of 031103130002520
 \___/\___/\___/
| | |
| | |____ network address
| |_________ area prefix
|______________ dnic

this is a summary of dnic's (taken from blade runner's file on itapac)

according to their country and network name.

dnic network name country dnic network name country

_______________________________________________________________________________
|
02041 datanet 1 netherlands | 03110 telenet usa
02062 dcs belgium | 03340 telepac mexico
02080 transpac france | 03400 udts-curacau curacau
02284 telepac switzerland | 04251 isranet israel
02322 datex-p austria | 04401 ddx-p japan
02329 radaus austria | 04408 venus-p japan
02342 pss uk | 04501 dacom-net south korea
02382 datapak denmark | 04542 intelpak singapore
02402 datapak sweden | 05052 austpac australia
02405 telepak sweden | 05053 midas australia
02442 finpak finland | 05252 telepac hong kong
02624 datex-p west germany | 05301 pacnet new zealand
02704 luxpac luxembourg | 06550 saponet south africa
02724 eirpak ireland | 07240 interdata brazil
03020 datapac canada | 07241 renpac brazil
03028 infogram canada | 09000 dialnet usa
03103 itt/udts usa | 07421 dompac french guiana
03106 tymnet usa |

there are two ways to find interesting addresses to connect to. the first
and easiest way is to obtain a copy of the lod/h telenet directory from the
lod/h technical journal #4 or 2600 magazine. jester sluggo also put out a good
list of non-us addresses in phrack inc. newsletter issue 21. these files will
tell you the nua, whether it will accept collect calls or not, what type of
computer system it is (if known) and who it belongs to (also if known.)
the second method of locating interesting addresses is to scan for them
manually. on telenet, you do not have to enter the 03110 dnic to connect to a
telenet host. so if you saw that 031104120006140 had a vax on it you wanted to
look at, you could type @c 412 614 (0's can be ignored most of the time.)
if this node allows collect billed connections, it will say 412 614
connected and then you'll possibly get an identifying header or just a
username: prompt. if it doesn't allow collect connections, it will give you a
message such as 412 614 refused collect connection with some error codes out to
the right, and return you to the @ prompt.
there are two primary ways to get around the refused collect message. the
first is to use a network user id (nui) to connect. an nui is a username/pw
combination that acts like a charge account on telenet. to collect to node
412 614 with nui junk4248, password 525332, i'd type the following:
@c 412 614,junk4248,525332 <---- the 525332 will *not* be echoed to the
screen. the problem with nui's is that they're hard to come by unless you're
a good social engineer with a thorough knowledge of telenet (in which case
you probably aren't reading this section), or you have someone who can
provide you with them.
the second way to connect is to use a private pad, either through an x.25
pad or through something like netlink off of a prime computer (more on these
two below.)
the prefix in a telenet nua oftentimes (not always) refers to the phone area
code that the computer is located in (i.e. 713 xxx would be a computer in
houston, texas.) if there's a particular area you're interested in, (say,
new york city 914), you could begin by typing @c 914 001 <cr>. if it connects,
you make a note of it and go on to 914 002. you do this until you've found
some interesting systems to play with.
not all systems are on a simple xxx yyy address. some go out to four or
five digits (914 2354), and some have decimal or numeric extensions
(422 121a = 422 121.01). you have to play with them, and you never know what
you're going to find. to fully scan out a prefix would take ten million
attempts per prefix. for example, if i want to scan 512 completely, i'd have
to start with 512 00000.00 and go through 512 00000.99, then increment the
address by 1 and try 512 00001.00 through 512 00001.99. a lot of scanning.
there are plenty of neat computers to play with in a 3-digit scan, however,
so don't go berserk with the extensions.
sometimes you'll attempt to connect and it will just be sitting there after
one or two minutes. in this case, you want to abort the connect attempt by
sending a hard break (this varies with different term programs, on procomm,
it's alt-b), and then when you get the @ prompt back, type 'd' for disconnect.
if you connect to a computer and wish to disconnect, you can type <cr> @
<cr> and you it should say telenet and then give you the @ prompt. from there,
type d to disconnect or cont to re-connect and continue your session
uninterrupted.

outdials, network servers, and pads

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
in addition to computers, an nua may connect you to several other things.
one of the most useful is the outdial. an outdial is nothing more than a modem
you can get to over telenet- similar to the pc pursuit concept, except that
these don't have passwords on them most of the time.
when you connect, you will get a message like 'hayes 1200 baud outdial,
detroit, mi', or 'ven-tel 212 modem', or possibly 'session 1234 established
on modem 5588'. the best way to figure out the commands on these is to
type ? or h or help- this will get you all the information that you need to
use one.
safety tip here- when you are hacking *any* system through a phone dialup,
always use an outdial or a diverter, especially if it is a local phone number
to you. more people get popped hacking on local computers than you can
imagine, intra-lata calls are the easiest things in the world to trace inexp-
ensively.
another nice trick you can do with an outdial is use the redial or macro
function that many of them have. first thing you do when you connect is to
invoke the 'redial last number' facility. this will dial the last number used,
which will be the one the person using it before you typed. write down the
number, as no one would be calling a number without a computer on it. this
is a good way to find new systems to hack. also, on a ventel modem, type 'd'
for display and it will display the five numbers stored as macros in the
modem's memory.
there are also different types of servers for remote local area networks
(lan) that have many machine all over the office or the nation connected to
them. i'll discuss identifying these later in the computer id section.
and finally, you may connect to something that says 'x.25 communication
pad' and then some more stuff, followed by a new @ prompt. this is a pad
just like the one you are on, except that all attempted connections are billed
to the pad, allowing you to connect to those nodes who earlier refused collect
connections.
 this also has the added bonus of confusing where you are connecting from.
when a packet is transmitted from pad to pad, it contains a header that has
the location you're calling from. for instance, when you first connected
to telenet, it might have said 212 44a connected if you called from the 212
area code. this means you were calling pad number 44a in the 212 area.
that 21244a will be sent out in the header of all packets leaving the pad.
once you connect to a private pad, however, all the packets going out
from *it* will have it's address on them, not yours. this can be a valuable
buffer between yourself and detection.

phone scanning
~~~~~~~~~~~~~~
finally, there's the time-honored method of computer hunting that was made
famous among the non-hacker crowd by that oh-so-technically-accurate movie
wargames. you pick a three digit phone prefix in your area and dial every
number from 0000 --> 9999 in that prefix, making a note of all the carriers
you find. there is software available to do this for nearly every computer
in the world, so you don't have to do it by hand.

part three: i've found a computer, now what?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
this next section is applicable universally. it doesn't matter how you
found this computer, it could be through a network, or it could be from
carrier scanning your high school's phone prefix, you've got this prompt
this prompt, what the hell is it?
i'm *not* going to attempt to tell you what to do once you're inside of
any of these operating systems. each one is worth several g-files in its
own right. i'm going to tell you how to identify and recognize certain
opsystems, how to approach hacking into them, and how to deal with something
that you've never seen before and have know idea what it is.

vms- the vax computer is made by digital equipment corporation (dec),

and runs the vms (virtual memory system) operating system.
vms is characterized by the 'username:' prompt. it will not tell
you if you've entered a valid username or not, and will disconnect
you after three bad login attempts. it also keeps track of all
failed login attempts and informs the owner of the account next time
s/he logs in how many bad login attempts were made on the account.
it is one of the most secure operating systems around from the
outside, but once you're in there are many things that you can do
to circumvent system security. the vax also has the best set of
help files in the world. just type help and read to your heart's
content.
common accounts/defaults: [username: password [[,password]] ]
system: operator or manager or system or syslib
operator: operator
systest: uetp
sysmaint: sysmaint or service or digital
field: field or service
guest: guest or unpassworded
demo: demo or unpassworded
decnet: decnet

dec-10- an earlier line of dec computer equipment, running the tops-10

operating system. these machines are recognized by their
'.' prompt. the dec-10/20 series are remarkably hacker-friendly,
 allowing you to enter several important commands without ever
logging into the system. accounts are in the format [xxx,yyy] where
xxx and yyy are integers. you can get a listing of the accounts and
the process names of everyone on the system before logging in with
the command .systat (for system status). if you seen an account
that reads [234,1001] bob jones, it might be wise to try bob or
jones or both for a password on this account. to login, you type
.login xxx,yyy and then type the password when prompted for it.
the system will allow you unlimited tries at an account, and does
not keep records of bad login attempts. it will also inform you
if the uic you're trying (uic = user identification code, 1,2 for
example) is bad.
common accounts/defaults:
1,2: syslib or operator or manager
2,7: maintain
5,30: games

unix- there are dozens of different machines out there that run unix.
while some might argue it isn't the best operating system in the
world, it is certainly the most widely used. a unix system will
usually have a prompt like 'login:' in lower case. unix also
will give you unlimited shots at logging in (in most cases), and
there is usually no log kept of bad attempts.
common accounts/defaults: (note that some systems are case
sensitive, so use lower case as a general rule. also, many times
the accounts will be unpassworded, you'll just drop right in!)
root: root
admin: admin
sysadmin: sysadmin or admin
unix: unix
uucp: uucp
rje: rje
guest: guest
demo: demo
daemon: daemon
sysbin: sysbin

prime- prime computer company's mainframe running the primos operating

system. the are easy to spot, as the greet you with
'primecon 18.23.05' or the like, depending on the version of the
operating system you run into. there will usually be no prompt
offered, it will just look like it's sitting there. at this point,
type 'login <username>'. if it is a pre-18.00.00 version of primos,
you can hit a bunch of ^c's for the password and you'll drop in.
unfortunately, most people are running versions 19+. primos also
comes with a good set of help files. one of the most useful
features of a prime on telenet is a facility called netlink. once
you're inside, type netlink and follow the help files. this allows
you to connect to nua's all over the world using the 'nc' command.
for example, to connect to nua 026245890040004, you would type
@nc :26245890040004 at the netlink prompt.
common accounts/defaults:
prime prime or primos
primos_cs prime or primos
primenet primenet
system system or prime
netlink netlink
test test
 guest guest
guest1 guest

hp-x000- this system is made by hewlett-packard. it is characterized by the

':' prompt. the hp has one of the more complicated login sequences
around- you type 'hello session name,username,accountname,group'.
fortunately, some of these fields can be left blank in many cases.
since any and all of these fields can be passworded, this is not
the easiest system to get into, except for the fact that there are
usually some unpassworded accounts around. in general, if the
defaults don't work, you'll have to brute force it using the
common password list (see below.) the hp-x000 runs the mpe operat-
ing system, the prompt for it will be a ':', just like the logon
prompt.
common accounts/defaults:
mgr.telesup,pub user: mgr acct: hponly grp: pub
mgr.hpoffice,pub unpassworded
manager.itf3000,pub unpassworded
field.support,pub user: fld, others unpassworded
mail.telesup,pub user: mail, others
unpassworded
mgr.rje unpassworded
field.hppl89 ,hppl87,hppl89,hppl96 unpassworded
mgr.telesup,pub,hponly,hp3 unpassworded

iris- iris stands for interactive real time information system. it orig-
inally ran on pdp-11's, but now runs on many other minis. you can
spot an iris by the 'welcome to "iris" r9.1.4 timesharing' banner,
and the account id? prompt. iris allows unlimited tries at hacking
in, and keeps no logs of bad attempts. i don't know any default
passwords, so just try the common ones from the password database
below.
common accounts:
manager
boss
software
demo
pdp8
pdp11
accounting

vm/cms- the vm/cms operating system runs in international business machines

(ibm) mainframes. when you connect to one of these, you will get
message similar to 'vm/370 online', and then give you a '.' prompt,
just like tops-10 does. to login, you type 'logon <username>'.
common accounts/defaults are:
autolog1: autolog or autolog1
cms: cms
cmsbatch: cms or cmsbatch
erep: erep
maint: maint or maintain
operatns: operatns or operator
operator: operator
rscs: rscs
smart: smart
sna: sna
vmtest: vmtest
 vmutil: vmutil
vtam: vtam

nos- nos stands for networking operating system, and runs on the cyber
computer made by control data corporation. nos identifies itself
quite readily, with a banner of 'welcome to the nos software
system. copyright control data 1978,1987'. the first prompt you
will get will be family:. just hit return here. then you'll get
a user name: prompt. usernames are typically 7 alpha-numerics
characters long, and are *extremely* site dependent. operator
accounts begin with a digit, such as 7etpdoc.
common accounts/defaults:
$system unknown
systemv unknown

decserver- this is not truly a computer system, but is a network server that
has many different machines available from it. a decserver will
say 'enter username>' when you first connect. this can be anything,
it doesn't matter, it's just an identifier. type 'c', as this is
the least conspicuous thing to enter. it will then present you
with a 'local>' prompt. from here, you type 'c <systemname>' to
connect to a system. to get a list of system names, type
'sh services' or 'sh nodes'. if you have any problems, online
help is available with the 'help' command. be sure and look for
services named 'modem' or 'dial' or something similar, these are
often outdial modems and can be useful!

gs/1- another type of network server. unlike a decserver, you can't

predict what prompt a gs/1 gateway is going to give you. the
default prompt it 'gs/1>', but this is redifinable by the
system administrator. to test for a gs/1, do a 'sh d'. if that
prints out a large list of defaults (terminal speed, prompt,
parity, etc...), you are on a gs/1. you connect in the same manner
as a decserver, typing 'c <systemname>'. to find out what systems
are available, do a 'sh n' or a 'sh c'. another trick is to do a
'sh m', which will sometimes show you a list of macros for logging
onto a system. if there is a macro named vax, for instance, type
'do vax'.

the above are the main system types in use today. there are
hundreds of minor variants on the above, but this should be
enough to get you started.

unresponsive systems
~~~~~~~~~~~~~~~~~~~~
occasionally you will connect to a system that will do nothing but sit
there. this is a frustrating feeling, but a methodical approach to the system
will yield a response if you take your time. the following list will usually
make *something* happen.
1) change your parity, data length, and stop bits. a system that won't re-
spond at 8n1 may react at 7e1 or 8e2 or 7s2. if you don't have a term
program that will let you set parity to even, odd, space, mark, and none,
with data length of 7 or 8, and 1 or 2 stop bits, go out and buy one.
while having a good term program isn't absolutely necessary, it sure is
helpful.
2) change baud rates. again, if your term program will let you choose odd
baud rates such as 600 or 1100, you will occasionally be able to penetrate
some very interesting systems, as most systems that depend on a strange
 baud rate seem to think that this is all the security they need...
3) send a series of <cr>'s.
4) send a hard break followed by a <cr>.
5) type a series of .'s (periods). the canadian network datapac responds
to this.
6) if you're getting garbage, hit an 'i'. tymnet responds to this, as does
a multilink ii.
7) begin sending control characters, starting with ^a --> ^z.
8) change terminal emulations. what your vt100 emulation thinks is garbage
may all of a sudden become crystal clear using adm-5 emulation. this also
relates to how good your term program is.
9) type login, hello, log, attach, connect, start, run, begin, logon, go,
join, help, and anything else you can think of.
10) if it's a dialin, call the numbers around it and see if a company
answers. if they do, try some social engineering.

brute force hacking

~~~~~~~~~~~~~~~~~~~
there will also be many occasions when the default passwords will not work
on an account. at this point, you can either go onto the next system on your
list, or you can try to 'brute-force' your way in by trying a large database
of passwords on that one account. be careful, though! this works fine on
systems that don't keep track of invalid logins, but on a system like a vms,
someone is going to have a heart attack if they come back and see '600 bad
login attempts since last session' on their account. there are also some
operating systems that disconnect after 'x' number of invalid login attempts
and refuse to allow any more attempts for one hour, or ten minutes, or some-
times until the next day.
the following list is taken from my own password database plus the data-
base of passwords that was used in the internet unix worm that was running
around in november of 1988. for a shorter group, try first names, computer
terms, and obvious things like 'secret', 'password', 'open', and the name
of the account. also try the name of the company that owns the computer
system (if known), the company initials, and things relating to the products
the company makes or deals with.

password list
=============

aaa daniel jester rascal

academia danny johnny really
ada dave joseph rebecca
adrian deb joshua remote
aerobics debbie judith rick
airplane deborah juggle reagan
albany december julia robot
albatross desperate kathleen robotics
albert develop kermit rolex
alex diet kernel ronald
alexander digital knight rosebud
algebra discovery lambda rosemary
alias disney larry roses
alpha dog lazarus ruben
alphabet drought lee rules
ama duncan leroy ruth
amy easy lewis sal
analog eatme light saxon
anchor edges lisa scheme
andy edwin louis scott
andrea egghead lynne scotty
animal eileen mac secret
answer einstein macintosh sensor
anything elephant mack serenity
arrow elizabeth maggot sex
arthur ellen magic shark
asshole emerald malcolm sharon
athena engine mark shit
atmosphere engineer markus shiva
bacchus enterprise marty shuttle
badass enzyme marvin simon
bailey euclid master simple
banana evelyn maurice singer
bandit extension merlin single
banks fairway mets smile
bass felicia michael smiles
batman fender michelle smooch
beauty fermat mike smother
beaver finite minimum snatch
beethoven flower minsky snoopy
beloved foolproof mogul soap
benz football moose socrates
beowulf format mozart spit
berkeley forsythe nancy spring
berlin fourier napoleon subway
beta fred network success
beverly friend newton summer
bob frighten next super
brenda fun olivia support
brian gabriel oracle surfer
bridget garfield orca suzanne
broadway gauss orwell tangerine
bumbling george osiris tape
cardinal gertrude outlaw target
carmen gibson oxford taylor
carolina ginger pacific telephone
caroline gnu painless temptation
castle golf pam tiger
cat golfer paper toggle
celtics gorgeous password tomato
change graham pat toyota
charles gryphon patricia trivial
charming guest penguin unhappy
charon guitar pete unicorn
chester hacker peter unknown
cigar harmony philip urchin
classic harold phoenix utility
coffee harvey pierre vicky
coke heinlein pizza virginia
collins hello plover warren
comrade help polynomial water
computer herbert praise weenie
condo honey prelude whatnot
condom horse prince whitney
cookie imperial protect will
cooper include pumpkin william
create ingres puppet willie
 creation innocuous rabbit winston
creator irishman rachmaninoff wizard
cretin isis rainbow wombat
daemon japan raindrop yosemite
dancer jessica random zap

part four: wrapping it up!

~~~~~~~~~~~~~~~~~~~~~~~~~~
i hope this file has been of some help in getting started. if you're
asking yourself the question 'why hack?', then you've probably wasted a lot
of time reading this, as you'll never understand. for those of you who
have read this and found it useful, please send a tax-deductible donation
of $5.00 (or more!) in the name of the legion of doom to:
the american cancer society
90 park avenue
new york, ny 10016

******************************************************************************
references:
1) introduction to itapac by blade runner
telecom security bulletin #1
2) the ibm vm/cms operating system by lex luthor
the lod/h technical journal #2
3) hacking the iris operating system by the leftist
the lod/h technical journal #3
4) hacking cdc's cyber by phrozen ghost
phrack inc. newsletter #18
5) usenet comp.risks digest (various authors, various issues)
6) usenet unix.wizards forum (various authors)
7) usenet info-vax forum (various authors)

recommended reading:
1) hackers by steven levy
2) out of the inner circle by bill landreth
3) turing's man by j. david bolter
4) soul of a new machine by tracy kidder
5) neuromancer, count zero, mona lisa overdrive, and burning chrome, all
by william gibson
6) reality hackers magazine c/o high frontiers, p.o. box 40271, berkeley,
california, 94704, 415-995-2606
7) any of the phrack inc. newsletters & lod/h technical journals you can find.

acknowledgements:
thanks to my wife for putting up with me.
thanks to lone wolf for the rsts & tops assistance.
thanks to android pope for proofreading, suggestions, and beer.
thanks to the urvile/necron 99 for proofreading & cyber info.
thanks to eric bloodaxe for wading through all the trash.
thanks to the users of phoenix project for their contributions.
thanks to altos computer systems, munich, for the chat system.
thanks to the various security personel who were willing to talk to
me about how they operate.