address>' or the internet address name, so I know
where is came from.
Address from. I will not include any for there are huge list that other
hackers have scanned out, and I would be just copying their
/ETC/PASSWD THIS IS THE FILE THAT YOU WANT, ISN'T IT ? I DO NOT THINK YOU
want John Jones mail. Well you could grab their mail, this
would be one way to do it.
netascii This how you want file transferred, you can also do it
Image, but i have never done this. I just leave it blank, and it
dose it for me.
& Welcome to the power of UNIX, it is multitasking, this little
symbol place at the end will allow you to do other things (such
as grab the passwd file from the UNIX that you are on).
Here is the set up:We want to get the passwd file from sunshine.ucsd.edu.
The file is copying to your 'home' directory is going to be named
* $ #tftp -g asunshine sunshine.ucsd.edu /etc/passwd &
Fingering is a real good way to get account on remote sites. Typing 'who'
of just 'finger ' you can have names to "finger". This
better chance of cracking that system. Here is a example of how to do it.
* % #who
* joeo ttyp0 Jun 10 21:50 (bmdlib.csm.edu)
* gatsby ttyp1 Jun 10 22:25 (foobar.plague.mil)
* bbc crp00 Jun 10 11:57 (aogpat.cs.pitt.edu)
* liliya display Jun 10 19:40
/and fingering what you see
* % #finger bbc
* Login name: bbc In real life: David Douglas Cornuelle
* Office: David D. Co
* Directory: //aogpat/users_local/bdc Shell: /bin/csh
* On since Jun 10 11:57:46 on crp00 from aogpat Phone 555-1212
* 52 minutes Idle Time
* Plan: I am a dumb fool!!
From there i can just call 'aogpat.cs.pit.edu' and try to hack it out.
Try the last name as the password, the first name, middle name and try them
all backwards (do i really need to explain it any more). The chances are real
If there are no users in line for you to type "who" you can just type
"last" and all the user who logged on will come rolling out, and "finger"
them. The only problem with using the last command is aborting it.
You can also try and call them and say you are the system manager, and
only on some systems....
I though I would add this as a reference guide to some common networks on
the Internet. If anything, you can know what people are talking about on some
AARNet - Australian Academic and Research Network, this network is to
support research for various Australian Universities. This
network supports TCP/IP, DECnet, and OSI (CLNS).
ARPANET - Getting sick of reading about this yet ? Well i am getting
sick of typing it.
BITNET - Because It's Time NETwork (BITNET) is a worldwide network that
connects many colleges and universities. This network uses many
different protocols, but it dose use the TCP/IP. Maybe you will
come across it.
CREN CSNET - Corporation for Research and Educational Network (CREN), The
Computer + Science research NETwork (CSNET). This network
links scientists at sites all over the world. CSNET providing
access to the Internet, CRET to BITNET. CREN being the name
CSUNET - California State University Network (CSUNET). This net
connects the California State University campuses and other
universities in California. This network is based on the CCITT
X.25 protocol, and also uses TCP/IP, SNA/DSLC, DECnet, etc etc.
The Cypress Net - This network started as a experimental network. The use
of this network today is to connection to the TCP/IP Internet
as a cheap price.
DRI - Dirty Rotten Oops, _Defense _Research _Internet is a WAN that
is used as a platform from which to work from. This network has
all kind of services, such as multicast service, real-time
conference etc. This network uses the TCP/IP (also see RFC
907-A for more information on this network).
ESnet - Is the new network by the Department of Energy Office of Energy
Research (DoE OER). This net is the backbone for all DoE OER
programs. This network replaced the High Energy Physics DECnet
(HEPnet) and also the Magnetic Fusion Energy network (MFEnet).
The protocols offered are IP/TCP, and also DECnet service.
JANET - JANET is a Joint Academic NETwork based in the UK, connected to
the Internet. JANET is a PSN (information has pass through a
PAD) using the protocol X.25 though it dose support the TCP/IP.
This network also connects PSS (Packet Switched Service is a
PSN that is owned and operated by British telecom).
JUNET - Japan's university message system using UUCP, the Internet
as its backbone, and X.25 (Confused, read RFC 877). This network
is also a part of USENET (this is the network news).
Los Nettos - Los Nettos is a high speed MAN in the Los Angeles area. This
network uses the IP/TCP.
MILNET - When ARPANET split, the DDN was created, thus MILNET (MILitary
NETwork) being apart of the network. MILNET is a unclassified,
along with three other classified networks which make up the
NORDUNet - This net is the backbone to the networks in the Nordic
Countries, Denmark (DENet), Finland (FUNET), Iceland (SURIS),
Norway (UNINETT), and Sweden (SUNET). NORDUnet supports TCP/IP,
DECNet, and X.25.
NSN - NASA Science Network (NSN), this network is for NASA to send and
relay information. The protocols used are TCP/IP and there is a
sister network called Space Physics Analysis Network (SPAM) for
ONet - Ontario Network is a TCP/IP network that is research network.
NSFNet - National Science Foundation Network, this network is in the
IP/TCP family but in any case it uses UDP (User Diagram
Protocol) and not TCP. NSFnet is the network for the US
scientific and engineering research community. Listed below are
all the NSFNet Sub-networks.
BARRNet - Bay Area Regional Research Network is a MAN in the San
Francisco area. This network uses TCP/IP. When on this
network be sure and stop into LBL and say hi to Cliff
Stool! Welp, I do not think there is a bigger fool!
(yeah I read his book too, i did not stop hacking for a
weeks after reading it).
CERFnet - California Education and Research Federation Network is
a research (welp, there is a lot of research going to in
the Internet, huh ?) based network supporting Southern
Californian Universities communication services. This
network uses TCP/IP.
CICNet - Committee on Institutional Cooperation. This network
services the BIG 10, and University of Chicago. This
JvNCnet - John von Neumann National Supercomputer Center. This
network uses TCP/IP.
Merit - Mert is a network connects Michigan's academic and
research computers. This network supports TCP/IP, X.25
and Ethernet for LANs.
MIDnet - MIDnet connects 18 universities and research centers in
the midwest US. The support protocols are TELNET, FTP
MRNet - Minnesota Regional Network, this network services
Minnesota. The network protocols are TCP/IP.
NEARnet - New England Academic and Research Network, connects
various research/educational institutions. You
can get more information about this net by mailing
'firstname.lastname@example.org'. That is if you have address
like I do.
NCSAnet - National Center for Supercomputing Applications
(hell, there is a network for this ? I can think of
a lot of application for it a Cray, Kracking K0dez
maybe?) supports the whole IP family (TCP, UDP, ICMP,
NWNet - North West Network provides service to the Northwestern
US, and Alaska. This network supports IP and DECnet.
NYSERNet - New York Service Network is a autonomous nonprofit
network. This network supports the TCP/IP.
OARnet - Ohio Academic Resources Network gives access to Ohio
Supercomputer Center. This network supports TCP/IP.
PREPnet - Pennsylvania Research and Economic Partnership is a
network run, operated and managed by Bell of
Pennsylvania. It supports TCP/IP.
PSCNET - Pittsburgh Supercomputer Center serving Pennsylvania,
Maryland, and Ohio. It supports TCP/IP, and DECnet.
SDSCnet - San Diego Super Computer Center is a network whose
goal is to support research in the field of science.
The Internet address is 'y1.ucsc.edu' or call Bob
at 619/534+5o6o and ask for a account on his Cray. I
am sure he will be happy to help you out.
Sesquinet - Sesquinet is a network based in Texas, TCP/IP are the
SURAnet - Southeastern Universities Research Association Network
is a network that connects southern institutions. It is
more of a south eastern connection, than a southern
THEnet - Texas Higher Education Network is a network that is run
by Texas A&M University. This network connects to host
USAN/NCAR - University SAtellite Network (USAN)/National Center
for Atmospheric Research is a network for the for
a information exchange.
Westnet - Westnet connects the western part of the US, not
including California. The network is supported by
Colorado State University.
USENET - USENET is the network news (the message base for the Internet).
This message base is the largest i have ever seen, with well
over 400 different topics, connecting 17 different countries.
I just read the security, unix bugs, and telco talk posts with
each of those subs having 100++ posts a day, i send a few hours
reading. There is just too much!!
TCP/IP is a general term, this means everything related to the whole
family of Internet protocols. The protocols in this family are IP, TCP, UDP,
the too in depth, as to not take up ten-thousand pages, and not to bore you,
f you want more information, get the RFCs. RFCs authors (yeah authors, some
RFC are books!!) are stuck up Ph.d.s in Computer Science, hell I am just some
TCP/IP protocol is a "layered" set of protocols. In this diagram taken
from RFC 1180 you will see how the protocol is layered when connection is
Figure is of a Basic TCP/IP Network Nodes
| Network Application |
| ... \ | / .. \ | / ... |
| ------- ------- |
| | TCP | | UDP | |
| ------- ------- |
| \ / | % Key %
| ------- --------- | ~~~~~~~
| | ARP | | IP | | UDP User Diagram Protocol
| ------- ------*-- | TCP Transfer Control Protocol
| \ | | IP Internet Protocol
| \ | | ENET Ethernet
| ------------- | ARP Address Resolution
| | ENET | | Protocol
| -------@----- | O Transceiver
| | | @ Ethernet Address
-------------- | ------------------ * IP address
TCP/IP: If connection is made is between the IP module and the TCP module
the packets are called a TCP datagram. TCP is responsible for making
sure that the commands get through the other end. It keeps track of
what is sent, and retransmits anything that does not go through. The
IP provides the basic service of getting TCP datagram from place to
place. It may seem like the TCP is doing all the work, this is true
in small networks, but when connection is made to a remote host on
the Internet (passing through several networks) this is a complex
job. Say I am connected from a server at UCSD, and I am connection
through to LSU (SURAnet) the data grams have to pass through a NSFnet
backbone. The IP has to keep track of all the data when the switch is
made at the NSFnet backbone from the TCP to the UDP. The only NSFnet
backbone that connects LSU is University of Maryland. U. of Maryland
has different circuit sets, thus having to pass through them. The
cable (trunk)/circuit types are the T1 (a basic 24-channel 1.544 Md/s
pulse code modulation used in the US) to a 56 Kbps. Keeping track of
all the data from the switch from T1 to 56Kbs and TCP to UDP is not
all it has to deal with. Datagrams on their way to the NSFnet
backbone (U. of Maryland) may take many different paths from the UCSD
All the TCP dose is break up the data into datagrams (manageable
chunks), and keeps track of the datagrams. The TCP keeps track of the
datagrams by placing a header at the front of each datagram. The
header contains 160 (20 octets) pieces of information about
the datagram. Some of the information in this is the sending FQDN to
the receiving FQDN (more over the port address, but Fully Qualified
Domain Name is a much better term). The datagrams are numbers in
octets (a group of eight binary digits, say there are 500 octets of
data, the numbering of the datagrams would be 0, next datagram 500,
next datagram 1000, 1500 etc.
UDP/IP: UDP is one of the two main protocols to count of the IP. In other
words the UDP works the same as TCP, it places a header on the data
you send, and passes it over to the IP for transportation through out
the internet. The difference is in it offers service to the user's
network application, thus it dose not maintain a end-to-end
connection, it just pushes the datagrams out!
connect to a system and get a message back saying "Host unreachable",
this is ICMP in action. This protocol is universal within the
Internet, because if it's nature. This protocol dose not use port
numbers in it's headers, since it talks to the network software it
Ethernet: Most of the networks use Ethernet. Ethernet is just a party line.
When packets are sent out on the Ethernet, every host on the Ethernet
sees them. To make sure the packets get to the right place the
Ethernet designers wanted to make sure that each address is different.
For this reason 48 bits are allocated for the Ethernet address, and a
built in Ethernet address on the Ethernet controller.
The Ethernet packets have a 14-octet header, this includes
address to and from. The Ethernet is not too secure, it is possible to
have the packets go to two places, thus someone can see just what you
are doing. You need to take note that the Ethernet is not connected to
the internet, in other words a host on the Ethernet and on the
Internet has to have both a Ethernet connection and a Internet server.
ARP ARP translates IP address to Ethernet address. A conversion table is
used (the table is called ARP Table) to convert the addresses. Thus
you would never even know if you were connected to the Ethernet
because you would be connecting to the IP address.
This is a real ruff description of a few Internet protocols, but if you
various hosts. Here is a list of RFC that are on the topic of protocols.
| RFC: | Description: |
| | |
| rfc1011 | Official Protocols of the Internet |
| rfc1009 | NSFnet gateway specifications |
| rfc1001/2 | netBIOS: networking for PC's |
| rfc894 | IP on Ethernet |
| rfc854/5 | telnet - protocols for remote logins |
| rfc793 | TCP |
| rfc792 | ICMP |
| rfc791 | IP |
| rfc768 | UDP |
| | |
This is for those of who like to know what they are doing, and when it
comes to address, you will know what you are looking at.
Internet address are long and hard to remember such as 22.214.171.124. If
you had to remember all the hosts you are on you would need a really good
memory which most people (like me) do not have. So Being humans (thus lazy)
All hosts registered on the Internet must have names that reflect
them domains under which they are registered. Such names are called Fully
Qualified Domain Names (FQDNs). Ok, lets take apart a name, and see such
^ ^ ^
| | |
| | |____ ``edu'' shows that this host is sponsored by a
| | educational related organization. This is a
| | top-level domain.
| |___________ ``berkeley'' is the second-level domain, this
| shows that it is an organization within UC
|__________________ ``lilac'' is the third-level domain, this indicates
the local host name is 'lilac'.
Here is a list of top-level domain you will run into.
| Common Top-Level Domains |
| COM - commercial enterprise |
| EDU - educational institutions |
| GOV - nonmilitary government agencies |
| MIL - military (non-classified) |
| NET - networking entities |
| ORG - nonprofit intuitions |
A network address is that numeric address of a host, gateway or TAC.
The address was though of with us in mind, meaning it is easy to scan
(war dial, wonder etc..). The address are maid up of four decimals numbered
classes that are used most, these are Class A, Class B, and Class C. I know
this has nothing to do with you, but I feel you should know what they are...
Class A - from '0' to '127'
Class B - from '128' to '191'
Class C - from '192' to '223'
Class A - Is for MILNET net hosts. The first part of the address has the
network number. The second is for the their physical PSN port
number, and the third is for the logical port number, since it is
on MILNET it is a MILNET host. The fourth part is for which PSN
is on. 126.96.36.199. '29' is the network it is on. '34' means it is
on port '34'. '9' is the PSN number.
Class B - This is for the Internet hosts, the first two "clumps" are for
the network portion. The second two are for the local port.
| |_____ Local portion of the address
|___________ Potation address.
Class C - The first three "clumps" is the network portion. And the last one
is the local port.
^ ^ ^ ^
\_|_/ |_____ Local Portation Address
|__________ Network Portation Address
When on a stolen account these are basic thing to do and not to do.
- Do not logon too late at night. All the manager has to
do is see when you logoned by typing "login". If it
sees 3 am to 5 am he is going to know that you were
in the system. I know, I love spending all night on a
account, but the best times are in the middle of the day
when the normal (the owner) would use the account. (NOTE
this is what they look for !)
- Do not leave files that were not there on *ANY*
directory, checks are sometimes made. This is on a
system security check list, which is normally done from
time to time.
- When hacking, do not try to hack a account more than
three times. It does show up on a logon file (when more
than three try are made on the same account !), and it
will also not let you logon on the account even if you
do get it right (NOTE this is not on all UNIX systems).
- Do not type in your handle ! you real name etc ..
- Encrypt all the mail you send.
- Leave VMS alone, VMS and TCP/IP do not mix well. It is
not worth your time. VMS is better for a X.25 network.
- DO send The Gatsby all the accounts you will get and
$ I would like to take this time to thank #
% Doctor Dissector for getting me on in the $
@ The Internet in the first place, and %
# for helping me correct the errors in @
$ the first release. #
@ The Gatsby 1991 %
This has been a AXiS Production!