300 lines
7.4 KiB
Plaintext
300 lines
7.4 KiB
Plaintext
r35
|
||
|
||
|
||
|
||
|
||
|
||
---------------------------------------
|
||
[ctrl-s pauses/space=quit]
|
||
|
||
uploaded by: the wizard of oz
|
||
|
||
es saying it's changed. but
|
||
they probably throw away those papers
|
||
and you will be able to find alot of
|
||
interesting inpho by trashing.
|
||
also, most or all calls to cosmos are
|
||
traced, or the number has ani equip
|
||
ment hooked up to it, so be careful!
|
||
|
||
|
||
identification:
|
||
---------------
|
||
|
||
cosmos logins and proceedures vary
|
||
from area to area, some ask for
|
||
just the login and password without
|
||
a wirecenter, others require it.
|
||
the phollowing information is based
|
||
on southern bell's cosmos system.
|
||
|
||
to identify a cosmos system after
|
||
connecting you will see:
|
||
|
||
;login:
|
||
password:
|
||
wc?
|
||
|
||
the ;login: is the username, which
|
||
usually consists of two letters and
|
||
two numbers ie: pa52. sometimes name:
|
||
is substituted for, or is required
|
||
with ;login: again it depends on what
|
||
system you are on. next it will ask
|
||
for the password: which depending on
|
||
the system, has different formats for
|
||
passwords. some make a little sense
|
||
like base52 while others may be eight
|
||
random characters. last thing you will
|
||
see is the wirecenter. a wirecenter
|
||
is usually an abbreviation of the city
|
||
that it covers. such as oa for oakland
|
||
or pp for pembroke pines, in any case
|
||
it is two letters. the wirecenter will
|
||
cover a certain amount of prefixes.
|
||
and you will not be able to look up
|
||
other phone #'s unless the prefixes
|
||
are in the specific wirecenter. the
|
||
promt for cosmos is the wirecenter and
|
||
a % sign. ie: wc% where wc is the wire
|
||
center you are logged in as. if you
|
||
do happen to get ahold of a login and
|
||
password, but the system still asks
|
||
for a wirecenter, then you can tell
|
||
what are valid wirecenters by when it
|
||
asks for login & password, then the
|
||
wirecenter and you enter a wrong wc
|
||
the system will respond with:
|
||
|
||
;login: pa52
|
||
password:
|
||
wc?xx
|
||
wc??
|
||
invalid login
|
||
|
||
if you noticed, wc?? came after the
|
||
wirecenter, now if you had a valid
|
||
wc, it would just say invalid login
|
||
after the wc without the wc??. ie:
|
||
|
||
;login:pa52
|
||
password:
|
||
wc?oa
|
||
invalid login
|
||
|
||
that would mean you have the correct
|
||
wc, but incorrect password. if all
|
||
goes well you will get oa% as the
|
||
promt for whatever your wc is.
|
||
|
||
transaction codes
|
||
----------- -----
|
||
|
||
cosmos has a set of three letter
|
||
commands called transaction codes
|
||
which tell the system what to do. they
|
||
enable you to view, modify, or add
|
||
information about telephone numbers,
|
||
class of service, operating exchanges,
|
||
etc.
|
||
|
||
here is a brief description of the
|
||
most commonly used transaction codes:
|
||
|
||
cay - create an assembly
|
||
cca - change customer attributes
|
||
day - delete an assembly
|
||
dre - deny and restore establishment
|
||
flr - frame layout report
|
||
ish - inquire about a ciruit <-phone #
|
||
loe - list originating line equipment
|
||
mal - manual assignment list
|
||
may - modify an assebly
|
||
mch - manually change hunt
|
||
mdc - manually disconnect a ciruit
|
||
sca - service order complection - auto
|
||
sir - sorting inquiry by range
|
||
slc - subscriber@tom calling features
|
||
usl - list usoc (us) file data
|
||
wcc - wire center change
|
||
|
||
here's an example of a transaction,
|
||
<EFBFBD><EFBFBD>ngDi<EFBFBD>h (inquire about a circuit)
|
||
which gives information about a
|
||
telephone number.
|
||
|
||
wc% ish
|
||
h tn 935-2481
|
||
_.
|
||
|
||
it will then print various information
|
||
about the phone # 935-2481. but it is
|
||
doubtful you will understand since it
|
||
is all abbreviated. i will explain
|
||
everything in part ii. after printing
|
||
the info about the #, cosmos will say:
|
||
** ish completed 20-jun-84 **
|
||
|
||
when using certain commands, there are
|
||
various lines to be used. some are:
|
||
h-line --required in most transactions
|
||
for order, inquiry, and report data.
|
||
i-line --transaction involves inward
|
||
movement (ie: installing a phone).
|
||
o-line --transaction involves outware
|
||
movement (ie: disconnecting a phone).
|
||
r-line -- used for making remarks to
|
||
service or work orders. a h-line was
|
||
used in this example.
|
||
to signify the end of input for most
|
||
commands type "." w/out quotes. you
|
||
use a ";" to separate ciruits, which
|
||
is good when you (or the phone co.)
|
||
has to enter massive amounts of info.
|
||
|
||
|
||
prefixes, formats and code values:
|
||
--------- ------- --- ---- -------
|
||
|
||
cosmos provides a language by means
|
||
of which the user can communicate with
|
||
the system. the language includes
|
||
various prefixes as well as input
|
||
formats and input values.
|
||
|
||
prefixes are abbreviations which
|
||
represent specific data categories to
|
||
the system when input by the user. an
|
||
example of a prefix is "tn" which means
|
||
"telephone number". an input format
|
||
defines the number of characters
|
||
following a prefix as well as the
|
||
pattern in which these must be entered
|
||
for example, "tn xxx-xxxx" means that
|
||
the prefix "tn" must be followed by
|
||
seven characters in the format shown.
|
||
|
||
input values are the allowable data
|
||
entered for each prefix in the correct
|
||
input format. as mentioned in the
|
||
previous paragraph, the input format
|
||
for the prefix "tn" is "tn xxx-xxxx".
|
||
the first three characters (xxx) must
|
||
be alphanumeric; the last four (xxxx)
|
||
must be numeric. so, cosmos would
|
||
consider an input of "tn 935-2481" as
|
||
valid input. but you *must* use the
|
||
correct wirecenter for the (xxx) in
|
||
question. in hacking cosmos part ii
|
||
i will have a list of the most
|
||
commonly used prefixes, formats and
|
||
prefix code values which enable you
|
||
to read and understand cosmos
|
||
transactions.
|
||
|
||
|
||
cosnix
|
||
------
|
||
|
||
cosnix is a mutated version of cosmos
|
||
and unix both written by bell labs.
|
||
cosnix, is the operating system of
|
||
the cosmos system.
|
||
|
||
system commands
|
||
------ --------
|
||
|
||
as some of you will notice,if you read
|
||
the basics of hacking ii- vax's unix,
|
||
by the knights of shadow, alot of the
|
||
commands used on unix are also used
|
||
on cosmos.
|
||
|
||
commands are as phollows:
|
||
|
||
where - gives location of the system:
|
||
this command can be $very$
|
||
useful since you can go
|
||
trashing at the location
|
||
that the center is at.
|
||
|
||
wc% where
|
||
|
||
cosmos 5 <- or whatever # it is.
|
||
street address
|
||
city, state zip
|
||
|
||
what - tells what version of cosnix
|
||
the system is running on.
|
||
|
||
wc% what
|
||
|
||
cosnix operating system 9.2.3 release
|
||
december 7,1983
|
||
14.2.2
|
||
march 1,1984
|
||
|
||
|
||
just like on a unix, to see who else
|
||
is on the system type:
|
||
|
||
wc% who
|
||
|
||
com3 tt00 gb
|
||
fw56 tt04 hh
|
||
pa52 tt12 pz
|
||
fc55 tt14 oa
|
||
rs52 tt15 pz
|
||
|
||
in the first column is the username,
|
||
the next is thier tt#, and last is
|
||
the wirecenter.
|
||
|
||
to see what files are in the directory
|
||
you are logged in on, type:
|
||
|
||
wc% ls
|
||
|
||
to see *all* files you have access to:
|
||
|
||
wc% ls /*
|
||
|
||
files and paths will be explained in
|
||
detail in parts ii, iii.
|
||
|
||
date - simply gives the date
|
||
|
||
tty
|
||
|
||
wc% tty<-will give you the teletypwrite
|
||
r
|
||
number you logged on as.
|
||
|
||
using control-c will interupt any
|
||
process you are executing at the time.
|
||
sometimes you will have to enter it
|
||
more than once. ctrl-s pauses ctrl-q
|
||
restarts and ctrl-y logs you off.
|
||
|
||
thats it for part i, it should give
|
||
you a basic understanding of cosmos.
|
||
part ii will explain the prefixes so
|
||
you will be able to interpret alot of
|
||
the information printed by cosmos.
|
||
and will explain paths/files.
|
||
|
||
acknowledgements: the warlock
|
||
tuc - tucbbs
|
||
agrajag the prolonged
|
||
|
||
|
||
|
||
|
||
---------------------------------------
|
||
|
||
|
||
|
||
|
||
|
||
8: Text Philez A-O
|
||
[UD:Punter][36 Min.][40]: |