From cronkite.ocis.temple.edu!astro.ocis.temple.edu!mart Fri Aug 11 02:41:28 1995
Path: cronkite.ocis.temple.edu!astro.ocis.temple.edu!mart
From: mart@astro.ocis.temple.edu (The Only Mart You Need)
Newsgroups: temple.unix
Subject: Just in case anyone forgot...
Date: 11 Aug 1995 02:07:23 GMT
Organization: Temple University, Academic Computer Services
Lines: 86
Message-ID: <40ee0r$t1i@cronkite.ocis.temple.edu>
NNTP-Posting-Host: astro.ocis.temple.edu
X-Newsreader: TIN [version 1.2 PL2]

This is the absolute funniest thing that ever happened while I was at
Temple.  Let's all just enjoy the crap out of it once again, for old 
times' sake.

					Luv u all...
						--Mart--
------
                 Hackers Guide to Temple University Networks
                                Dec 19, 1994 


FOREWORD
	
	It was our understanding that the first HGTUN is outdated at this
monent, so the decision was made to make up the second version of the guide.
Bear in mind that this version of HGTUN does not have anything in common
with the first release. We hope that this version will give you more
extended information. Happy hacking.



GENERAL INFORMATION

	The physical layer of the TU network is mainly 10 Mb ethernet,
although most of routes between buildings are fiber. The Ambler and Tyler
campus are connected to main TU system using ISDN line rented from the Bell
Atlantic. There are also 3 known to us token ring networks that right now
are bridged over ethernet. There is also one known to us old coaxile cable
that connects Cornwell hall to the University Service Building. This is also
a bridged route. The link to outside world is provided by the PREPnet and
gives TU 2 T-1 channels, that are connected directly to PREPnet routers that
are connected to JvNcNET, ANS-net, cix and other main backbones. This gives
Temple trip of less than 15 hops to most of American destinations and less
then 30 hops to most of destinations around the world.
	In 1994 TU started to move from "non-backbone"

ROUTING
-------

	Temple has really screwed up routing system, even equipment they
have would provide efficient routing for a university of a bigger size.
Temple uses mainly Welfleet and CISCO routers. Since Temple started to move
to a "secure backbone" every building either has a working router, has a
router that they can not configure properly, or will have a router in the
nearest (or not) future. 
	Routers are setted up or a to be setted up with ability to route IP,
IPX and Apple Talk packets over a "secure backbone". When I heared about
combination of IPX/AppleTalk and the concept of "secure backbone" I
basically fall out from the chair. 

COMMENTS ABOUT NETWORK SECURITY
-------------------------------

	Temple has nothing that can be called network security what-so-ever.
There is no one in official positions that would be able to prevent you from
taking over most of networks in Temple University. WARNING: I SAID MOST of
networks AND I'M NOT JOKING. The following are networks that I would NOT
touch if I WERE YOU. They are all in the CIS Department of Temple
University.

	TREX-net (TREX-net SERVERS: trex-1.cis.temple.edu 
				    trex-2.cis.temple.edu
				    trex-3.cis.temple.edu
				    trex-4.cis.temple.edu
				    trex-5.cis.temple.edu)
	TREX-net workstations: all computers with IPs 155.247.179.xx

	The incidents over last couple of month made it pretty clear that
YODA.CIS.TEMPLE.EDU and its subnet the most, Snowhite.cis.temple.edu and its
subnet are not recommended to be broken into. It is reasonable to expect
that several other systems in the CIS department, namely JEDI, THEFORCE and
BIGBOY are not recommened to be broken into. 
	This is all due to fact that one of routine lists of directoties in
/usr/preserve on Astro.ocis.temple.edu indicated that one of the top rated
"Ghostbusters", the Russian DEVIL (AKAs: F1R3F0x, Iron Eagle, JaGuAr) is in
Temple University. Belive me, you do not, do not want to mess with this
person. If you are attacking those computers, you are committing a suicide.  
We have a certain concern that one day we wil realize that this persons take
over the network security department of this university. If this is true,
then we will update this guide as soon as possible. But also I wish to give
you a hint: according to my knowledge he will never move even one finger to
help computers in a *.main.temple.edu (i.e. computers in the University
Service Building) due to some misunderstanding with one of the bosses that
costed him a lot, and computers.

COMPUTER SYSTEMS IN TEMPLE UNIVERSITY