gemini - kennedy.gemi.dev

💾 Archived View for clemat.is › saccophore › library › ezines › textfiles › ezines › K1INE › k-1ine_… captured on 2022-01-08 at 16:17:38.

-=-=-=-=-=-=-

k-15-(7)-01

OoO=o=oOO=o=O=OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
OoO=o=oOO=o=O=OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
OoO=o=oOO=o=O=>
: -`- -`- OoO=o=oOO=o=O=>
; _|_--oOO--(_)--OOo--_|_ OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
| � K-1ine Zine ! | OoO=o=oOO=o=O=>
! issue 15, volume 7 � OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
---------O^O---- OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
;. |__|__| OoO=o=oOO=o=O=OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
|| || OoO=o=oOO=o=O=OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
ooO Ooo OoO=o=oOO=o=O= OoO=o=oOO=o=O=OoO=o=oOO=o=O=>
OoO=o=oOO=o=O=OoO=o=oOO=o=O=LoveO=o=oOO=o=O=OoO=o=>
;`-.> May 2001 <=o=O=o=O=o=O

'Bombs Not Food'

'The Associated Press is neither radical, passionate nor accurate.'

_____________________________________________________________________________

� .- Words from the Editor -. � |

: [-] Introduction .......................................... The Clone :*
: (-) Contact Information ................................... The Clone :*
: (-) Affiliate Web-Links ................................... Nettwerked :*
: (-) News: Nettwerked CD ................................... The Clone :*
: (-) Advertisment .......................................... HackerSalvage:*
: (-) Advertisment .......................................... FlipperSmack :*
: (-) Link of the Month ..................................... The Clone :*
: (-) Miscellaneous Links ................................... The Clone :*
: (-) K-1ine Mirrors ........................................ The Clone :*

____________________________________________________________________________

� .- Documents -. � |

: (x) 'WNN Exclusive' ....................................... WNN :*
: (x) 'Tesla Coil Instructions' ............................. Nikola Tesla :*
: (x) 'Stellar 310 - Guide and Specifications' .............. Nettwerked :*
: (x) 'Nevada Probes Vegas Phone Hacks'...................... Cenobyte :*
: (x) 'Poem By Wizbone' ..................................... Wizbone :*
: (x) 'GUTSCI Protocol' ..................................... Fractal :*

_____________________________________________________________________________

� .- Conclusion -. � |

: [-] Credits ............................................... The Clone :*
: [-] Shouts ................................................ The Clone :*

_____________________________________________________________________________

Introduction --

Hello to all the avid K-1ine readers, and to all the newbies who happened
to stumble across my crazy collection of articles in the premier 21st century
Canadian hacking and phreaking electronic magazine.

If you have noticed, I am now including not only technical articles, but
interesting scientific news articles as well in an attempt to enlighten the
masses and open up the reader scope by many-a-soul.

So please enjoy the 15th issue, 7th volume, of K-1ine and go ahead -

learn something.

-->
Contact Information;
=-=-=-=-=-=-==-=-=-=

Comments/Questions/Submissions: theclone@hackcanada.com

On IRC: irc.h410g3n.com, #altphreakingfaq, #cpu (key required),
#hackcanada, #k-1ine

Shoot me an ICQ message: (UIN) 79198218

Check out my site: (Nettwerked) http://www.nettwerked.net

-->

Affiliate Web-Links:
=-=-=-=-=-=-==-=-=-=

B0G http://www.b0g.org
Damage Incorporated http://www.freeyellow.com/members6/damage-inc/index.html
Fuck Rogers AT&T http://www.fuckrogersatt.com *
Grass Hopper Unit http://www.ghu.ca
Hack Canada http://www.hackcanada.com
Phreak BC http://www.phreakbc.com
PyroFreak http://www.multimania.com/pyrozine/index.html
TRAPFONE http://www.trapfone.com *

= featured sites of Nettwerked Incorporated

-->

News: Nettwerked CD

[Tue May 8 21:43]

I just wanted to fill you all in on what is happening with the
Nettwerked CDs (www.nettwerked.net/cd.html) that Cenobyte, DWR,
and I are working our butts off to finish for sale at Def Con 9.

As it stands, we will not be featuring any mainstream artists in
the cd without their express written permission (Cenobyte is working
on getting our stuff to 'Orbital' for permission to use 'Halcyon & On & On'
for our opening song). DWR and I however have finished off two down-tempo/
experimental tracks for the cd's; "The Sine Wave Experiment" and "Funk".
We plan on writing more songs in the future (using 'FruityLoops') ...
maybe some hard-trance stuff... and more experimental/downtempo (we love
that shit).

Now, if you make music on your computer (we prefer if it's electronic;
ie. trance, ambient, experimental, jungle, drum & bass, hardhouse, hardcore,
dub, etc) and would like to see your masterpiece(s) on the Nettwerked cd,
please contact either me (The Clone): theclone@ecn.ab.ca and/or Cenobyte:
jkodish@ecn.ab.ca.

[ Nettwerked Discussion Board 2.0 ]
[ http://disc.server.com/discussion.cgi?id=150061&article=299 ]

-- Advertisment --

+++ WWW.HACKERSALVAGE.COM +++

HackerSalvage.com is a non-profit website dedicated to
keeping old hardware in circulation. Many of us have
piles of it sitting around but can't just toss it out.
Here you can post computer items for sale or post a
want ad for items you are looking for. A perfect place
to get rid of perfectly good junk.... and get some new
stuff to rebuild the pile.
+++ +++

Flippersmack AD -

"Flippersmack is a culturemag for a penguin generation. What does this
mean? Articles and reviews from your favorite writers. The low-down on
what's fresh in tech, comics, movies, and music. Wrapped in a style all
its own."

"We will strive to release Flippersmack every week; a taste of insanity to
inspire, inform, and entertain. From the creators of System Failure and
Avalanche, there's a new zine out on the net: FLIPPERSMACK!"

You can read the first six issues at:

http://www.nettwerked.net/flippersmack001.txt
http://www.nettwerked.net/flippersmack002.txt
http://www.nettwerked.net/flippersmack003.txt
http://www.nettwerked.net/flippersmack004.txt
http://www.nettwerked.net/flippersmack005.txt
http://www.nettwerked.net/flippersmack006.txt

--=[ LINK OF THE MONTH ]=--

From now on, I will be posting one really great "link of the month" on
future issues of K-1ine magazine. The link can be anything in the technology
industry, music scene, rave scene, punk scene, or even a good article you
read on a news site. I'll be taking submissions via e-mail, ICQ, or IRC right
away; so get your links in and maybe you'll see it in the next issue of K-1ine!

For the month of May, the link of the month is:

The Secret guides to - Health
- Wealth
- Wisdom

http://www.waynegreen.com

[submitted by: The Clone]

K-1ine Mirrors:

http://the.wiretapped.net/security/info/textfiles/k1ine/

"Wiretapped.net is an Australian site offering an archive of open
source software, informational and advisory textfiles and radio/conference
broadcasts covering the areas of network security, network operations,
host integrity, cryptography and privacy. We aim to become the largest
archive of this nature in the Asia/Pacific region through steady growth
of our archives and regular updates to them (most updated nightly).
We are proudly telehoused on a 10Mbit/sec connection by Connect.com.au using
OneGuard hardware donated by eSec Limited. The archive, along with its
sister site on the same machine, The AusMac Archive, generates between 10
and 60 gigabytes of outbound traffic daily. Wiretapped.net is hosted in
Sydney, Australia."

-
<bu-joe> i want to be quoted in k-1ine then and only then will i be truly
happy.
-

WNN Exclusive
04/24/01

As always, WNN's dedicated effort to expose the truth has once again
turned up some secrets. This time is seems our friends The Clone, editor
in chief of k-line magazine and webmaster of security sites such as
nettwerked.net and trapfone.com has more secrets.

As it turns out, The Clone, aka Rebecca Fitzgerald, sleeps with a pink
teddy bear. Yes, it's true. He, a grown man, and seemingly level-headed
individual sleeps with a pink, stuffed teddy bear purchased from Zellers.

He affectionately calls his child's plaything "Muffy" and has been said to
cry quite violently when it's removed from his bedroom.

WNN staff discovered this while investigating his living premises while he
was at work. As yet, WNN hasn't been able to find out just where The
Clone's place of employment is. A hidden camera was placed in Clone's
bedroom and the teddy removed. The following is an ascii conversion of
what the camera picked up when The Clone returned home to find his beloved
"Muffy" not on the silk pillow where he leaves it every morning.

____________
\ ####### \ /0\
\ pillow \ \|/
\ ####### \ | The Clone
\ \ /`\
\ bed \ _| \_
\___________\

As you can see from the shocked look on The Clone's face, he was quite
distraught by the whole situation. Moments later, the camera caught Clone
crying furiously and banging his fists on the wall. WNN officials parked
in a white van outside, watching the ordeal eventually felt sorry for The
Clone and left the bear on his doorstep, rang the doorbell, and gracefully
ran away.

Sensitive young man, or derranged teddy-loving psychopath? You decide.

-
<Tiffany> i think we're alone now... clonie clonie clonie i want your bone now
-

Tesla Coil Instructions

Note: These are instructions for building a Tesla Coil exactly like
the one shown on the photos page. It may be beneficial to change some
things.

Materials

1. Particle board

2. 4.5" PVC pipe

3. 4.5" PVC flange

4. 6.25" flexible duct

5. 22 AWG magnet wire

6. 1/4" copper tubing

7. 270VA Neon transformer: 9000V Secondary; 120V Primary

8. Glass wine bottles

9. Salt

10. RTV

11. Screwable pop bottle caps

12. Flat black spray paint

13. Drill

14. Saw

15. Polyurethane

16. Polyeurathane brush

17. 3/4" copper pipe

18. Plastic for mounting copper pipe

19. Pipe cutters

20. Wire cutters

21. Screws

22. Bolts

23. Nuts

24. Washers

25. Screwdriver

26. Wrench

27. Aluminum foil

28. Glass

29. Electrical tape

30. Blow torch

31. Solder

32. Flux

33. Fishing line

34. 14AWG High-voltage wire (15,000V)

35. Ring terminals

36. Multi-meter capable of measuring capacitance

39. Tape measure

Procedure

1. Fill the 8 wine bottles with saturated salt water up to where the
bottles start to curve. Fill the rest of the bottles up with motor
oil. Drill a hole in the center of each pop cap and put a bolt through
the hole upside down. Place a wire connector on the top of the caps.
Seal the caps with RTV. Wrap the bottles in aluminum foil so that no
salt water can be seen. Wrap electrical taped around the sides of the
bottles. The bottoms should have foil, but no electrical tape. Build a
box to put the eight bottles in and spray paint it flat black. The
bottles should fit snugly. Place a piece of glass on the bottom of the
box and put aluminum foil over it, and then put the bottles in the
box.

2. Build 6 supports for the primary coil using particle board. There
should be a 30 degree angle of elevation, an effective height of 3.5",
and an effective width of 6" on each one. Cut 15 grooves on the tops
of them. Wrap the copper tubing in a spiral using the grooves.

3. Wrap the 22 gauge magnet wire around the PVC pipe and put
polyurethane over the coil.

4. Make the spark gap by using RTV to put the copper pipe on the
plastic. There should be a .03" gap between each one.

5. Use the ducting to construct a toroid with a 29.2" outside
diameter.

6. Secure the primary coil, secondary coil, spark gap, capacitor box,
and transformer to a piece of particle board. Hang the toroid from the
piece of PVC pipe with two perpendicular pieces of fishing line.

7. Wire the two circuits as shown below.

[http://www.nettwerked.net/tesla.bmp]

"The mind of a genius lives forever"

Rest In Peace, Nikola Tesla

-
<CHadder> "hey mr ss man, is your phone running?" "ugh... yes...?" "then a
demostrater put lsd in your donut, haw haw"
-

Stellar 310 - Guide and Specifications

date. 05.15.01

INTRODUCTION

This phone has been specifically configured for Semi-Public
applications. Responsibility for the type of use of the phone, call
rates, and any federal, state, or local regulations are at the sole
discretion of the telephone owner. It is recommended that you contact
your state PUC (Public Utilities Commission) or state PSC (Public
Service Commission) regarding questions about product application.

Your Payphone's Programming

Your S-310 payphone has been pre-programmed to your request by G-TEL &
should be ready to work once it is properly installed.

Special Note to Payphone Owner

1. It is strongly recommended that all key numbers related to your
payphone(s) be recorded in case of loss or theft. G-TEL Enterprises,
Inc. is not responsible for keeping records of customer's key numbers.

Upper Housing Key Number(s):_____________________________________________

Lower Housing Key
Number(s):_____________________________________________

2. It is strongly recommended that you establish & use the Coin Box
Amount Security Code feature to prevent the coin box from
over-filling. The coin box amount should not exceed $150.00.
Over-filling of the coin box can lead to the malfunction of
several major components of the payphone.

Coin Box Amount Security Code: *#________________________

Technical Support

G-TEL Enterprises, Inc. offers technical support via telephone &
Internet only. Before trying to contact G-TEL Technical Support, we
strongly advise that you read the portion of the manual related to
your support needs so that a technician will be able to better assist
you.

G-TEL Technical Support via e-mail: support@payphone.com

G-TEL Technical Support via phone: 1-800-884-4835

MOUNTING INSTRUCTIONS

Mounting the Backboard or Enclosure

OUTDOOR INSTALLATION

If the payphone is to be installed outdoors, you must use an outdoor
pedestal / enclosure to mount the payphone and to prevent weather
deterioration. Outdoor pedestals can be mounted using concrete
anchors. Outdoor wall-peds can be mounted using toggle bolts. The
telephone cable should be routed to the pedestal using EMT conduit.
Once the pedestal & enclosure is mounted, follow the instructions
in this guide to mount the payphone to the pedestal & enclosure.

INDOOR INSTALLATION

It is recommended to use �" Toggle Bolts (with washers) to secure
the backboard or enclosure to the wall. The length of the toggle bolt
depends on the thickness of the wall. Anchor Screws may be used as an
alternative to Toggle Bolts.

1. Ensure that the wall that the backboard or enclosure is to install
to is flat & level.

2. The top height of the backboard or enclosure should be determined
by the following:

- Standard Height = 63" from floor

- Wheelchair Accessible = 54" from floor

3. Place the backboard or enclosure against the wall at the desired
height & mark the Line Wire Entrance Hole & Mounting Holes to be used,
(the backboard or enclosure offers 10 mounting holes, although not all
10 must be used.) Use the diagram below to ensure the backboard or
enclosure is not upside down or backwards.

4. Drill through the marked holes on the wall using a drill bit similar
to the size of the toggles being used.

5. Route the telephone line cable through the Line Wire Entrance Hole.

6. Insert each toggle bolt & washer through the mounting holes being
used on the backboard or enclosure.

7. Secure the backboard or enclosure against the wall through the
pre-drilled holes & tighten each toggle bolt.

Separating the Upper & Lower Housing

1. Insert the upper housing key into the upper housing lock (located
on the right side of the phone) & turn it 1/8 turn counter clockwise.

2. Insert the T-wrench key into the T- wrench insert (located approx.
6 inches above the upper housing lock) & turn it 1/8 turn clockwise,
until you hear the phone `snap' open.

3. Slide the upper housing away from the lower housing (make sure the
upper housing cable is disconnected from the circuit board.)

Removing the Circuit Board Chassis

1. Disconnect the 4-wire Trigger Switch plug, (blue, red, white, &
green plug.)

2. Disconnect the 3-wire Relay plug (green, red, & white plug.)

3. Disconnect the modular RJ11 Telephone Line connector.

4. Disconnect the circuit board Ground wire.

5. Loosen the Captive nut at the bottom left of the circuit board
chassis.

6. Remove the circuit board chassis by carefully pulling down & away
from the inside of the lower housing.

Removing the Coin Acceptor

1. Remove the coin reject chute from the coin acceptor by loosening
the screw that attaches the top of the reject chute to the bottom of
the coin acceptor.

2. Loosen the slotted nut at the top rear of the coin acceptor.

3. Remove the coin acceptor by pulling it up & then outward, away from
the inside of the lower housing.

Removing the Vault Door & Coin Box

1. Insert the lower housing key into the lock on the left side of the
lower housing & turn it � turn counter-clockwise.

2. Insert the T-wrench key into the vault door's vertical T-wrench key
insert (located at the center of the vault door) & turn it 1/8 turn
clockwise.

3. Remove the vault door & the coin box from the vault area.

Securing the Lower Housing to the Mounting Surface

1. Insert the telephone line cable through the line wire entrance hole.

2. Secure the lower housing to the backboard or enclosure mounting
surface using seven � x 20 x � mounting screws.

Reinstalling the Coin Box & Vault Door

1. Insert the coin box inside the vault area of the lower housing.

2. Make sure the lower housing key is in the unlock position.

3. Insert the T-wrench key into the vault door's vertical T-wrench key
insert (located at the center of the vault door) & turn it � turn
clockwise.

4. Insert the vault door into the lower housing vault area & turn the
T-wrench key � turn counter-clockwise to secure it.

5. Turn the lower housing key clockwise to the lock position & remove
the key.

Reinstalling the Coin Acceptor

*READ TO INSURE PROPER COIN ALIGNMENT*

1. Before re-installing the coin acceptor, ensure that the trigger
switch unit that the coin acceptor installs on top of is firmly
secured into the trigger switch sleeve in the back of the lower
housing, (the trigger switch should not be loose.)

2. Guide the tab at the bottom rear of the coin acceptor into the rear
of the trigger switch.

3. Position the top of the coin acceptor bracket onto the rear lip of
the coin acceptor slotted nut & then tighten the nut.

4. Reinstall the coin reject chute & secure the screw at the top of
the reject chute to the bottom threads of the coin acceptor.

Reinstalling the Circuit Board Chassis

1. Install the circuit board chassis by guiding the tab at the top,
left of the chassis into the slot at the top, left of the lower
housing. As you position tab, guide the captive nut onto the mounting
stud of the lower left side of the lower housing & then tighten it.

2. Connect the 4-wire Trigger Switch plug to the 4-prong Trigger Switch
connector.

3. Connect the 3-wire Relay plug to the 3-prong Relay connector.

4. Connect the RJ11 modular plug to the Telephone Line connector.

5. Connect the circuit board Ground wire to the middle right terminal
of the terminal block.

6. Connect the Battery plug (black & red wire plug) to the Battery
connector of the circuit board. (The battery is not usually connected
at the factory. To prevent the battery from draining, do not connect
the battery until the telephone line is ready to be connected.)

Connecting the Telephone Line

A minimum of 22ma (& 44 VDC) loop current must be provided to the
payphone from the Telephone Company's Central Office. In certain
situations, due to the distance between the Central Office and the
phone site, the loop current may not meet the required level of 22ma.
If the loop current is below 22ma, dial tone may not occur or the
phone may experience only momentary burst of dial tone. It is
recommended that the loop current level at the phone be tested at this
time to ensure that the required loop current level is present.

1. It is recommended that standard telephone / communication cable
(No. 22 gauge, 2 pair or greater) be used to connect the telephone
line with the payphone. Telephone / Communication cable usually
consists of 2 or more pairs of color-coded wire.

2. Connect one pair of communication cable wire to the two points of
the Telco interface box (D Marc location) that the telephone line
originates from.

3. Connect the opposite end of the same pair of wire to the top left &
bottom left terminal screws, (terminal block is located on the base of
the payphone's lower housing.)

4. Connect a proper earth ground wire to the left middle terminal to
ensure safety.

If using a line cord with a modular RJ11 plug instead of telephone /
communication cable, disregard the RJ11 pigtail cord that originates
from the terminal screws. Instead, plug in your incoming telephone
line-cord directly to the circuit board RJ11 connector.

Re-Connecting the Upper & Lower Housing

1. Connect the upper housing dial / hookswitch ribbon cable to the
circuit board upper housing connector.

2. Make sure the upper housing key is in the unlock position & the "T"
wrench key is in the open position, (all the way forward.)

3. Slide the bottom-lining of the upper housing along the lining of the
lower housing until the two housings meet.

4. Turn the T-wrench key 1/8 turn counter-clockwise until it `snaps'
close & then remove both keys.

PROGRAMMING INSTRUCTIONS

Your Payphone's Programming

Your S-310 payphone has been pre-programmed to your request by G-TEL &
should be ready to work once it is properly installed.

If you were unable to provide us with your programming request at
the time of your order, please test the payphone to see if it charging
acceptable amounts for local, toll, long distance, & other types of
calls. By simply dialing any number, the payphone will give voice
prompts of the required amount of money of the call if there is a
charge. Below is a list of typical programming the payphone will
usually contain if the customer was unable to provide us with
programming request at the time of their order.

If you are experiencing problems with the current programming
set-up or have questions on how to change the current programming,
please contact G-TEL Technical Support by phone at 1-800-884-4835 or
by e-mail at support@payphone.com.

Typical Pre-Sets for S-310 Payphones Not Pre-programmed to Customers
Request

7-Digit Calls; $.35 every 15 minutes

10-Digit Home Area Code Calls; $1.00 every 2 minutes

Long Distance Calls in U.S; $1.00 every 2 minutes

Information Calls; $.75

1-800 Type Calls; Free

Incoming Calls; Free

If you are a customer using Protel ExpressNet Payphone Management
software, please refer to your Protel Pocket Reference Guide & your
ExpressNet Manual for instructions on Initializing & Programming the
Payphone.

Entering the Program Mode

This procedure, among others, is necessary if you are editing the
current programming set-up. All program entries are done in the
program mode, using the keypad of the payphone. When programming, one
`beep' represents a completed entry. Three `beeps' represents an
error. To start an entry over, press the # key & wait for three
`beeps' & then re-try the entry. If you make a mistake on one entry,
you do not have to re-do all other entries.

1. Open the upper housing of the payphone, (see Separating the Upper &
Lower Housing on pg. 4.)

2. Ensure that the telephone line, dial / hookswitch ribbon cable, &
circuit board battery have all been properly connected, (see Circuit
Board Diagram below).

3. Push & hold the black program button on the circuit board, (see
Circuit Board Diagram below.)

4. Take the handset off-hook, (while program button is held down.)

5. Listen for a single `beep'

6. Release the program button (after the single `beep' is heard.)

Programming the Rate, Time Limit, & Keypad Allowance

The rate, time limit, and keypad allowance features are edited in the same
program entry for each type of call. Therefore, you must program for each
feature even if only trying to change one of these features. Before you
begin programming, you must first locate the Rate Band (4-digit code) that
represents the type of call you are programming for, (see the Call Type
Description Table above.)

1. Make sure the phone is in the program mode.

2. Enter the following information in this order
for the call being programmed:

4-digit Rate Band, (see Call Type Description Table for list of Rate Bands)

4-digit Initial Charge, (if the call is free, enter 0000)

4-digit Additional Charge, (if the call is free or unlimited, enter 0000)

3-digit Initial Time Limit, (if the call is free or unlimited, enter 255)

2-digit Additional Time Limit, (if the call is free or unlimited, enter 01)

4-digit Keypad Allowance, (if the keypad is allowed during the call,
enter 0008; if the keypad is not allowed during the call, enter 0001)

Press the * (star) key to complete the entry; listen for one confirmation
`beep'

Changing the Receiver Volume Level

1. Make sure the phone is in the program mode.

2. Enter 27

3. Enter the receiver volume level. (1=Lowest 2=Medium 3=Highest)

4. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

To Disable Certain Types of Calls

1. Make sure the phone is in the program mode.

2. Enter the 4-digit rate band of the type of call being disabled (see
Call Type Description Table on page 11 for help)

3. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

To Program Certain Types of Calls to be Free

1. Make sure the phone is in the program mode.

2. Enter the 4-digit rate band of the type of call being made free
(see Call Type Description Table on page 11 for help)

3. Enter 0000 0000 255 01 0008 *

4. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

Programming an Access Code for PBX Phone Systems

The following procedure shows the steps necessary to allow the S-310
to work on a PBX phone system when an access code must be dialed to
access an outside line. The S-310 will automatically dial the PBX
access code before the users destination number.

1. Make sure the phone is in the program mode.

2. Enter 24

3. Enter the PBX access code.

4. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

Programming a Free Number

1. Make sure the phone is in the program mode.

2. Enter 23

3. Enter the free number exactly as it would normally be dialed from
the payphone.

4. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

To delete a free number that has been programmed, enter 23 *
*NOTE Only one free number may be programmed into the phone.

COIN BOX AMOUNT SECURITY CODE

Overfilling of the coin box can cause several major components of the
payphone to malfunction. To prevent the coin box from overfilling,
the owner should use the coin box amount security code to check the
status of the coin box. The coin box amount should not exceed 150.00.

Programming the Coin Box Amount Security Code

1. Make sure the phone is in the program mode.

2. Enter 293

3. Enter any 4-digit code except 0000

4. Press the * (star) key to complete the entry; listen for one
confirmation `beep'.

Exit the program mode & reset the coin box amount to 0 zero, (see
Re-Setting the Coin Box Amount to Zero below)

Re-Setting the Coin Box Amount to Zero

1. Lift the handset off-hook & listen for dial tone.

2. Dial * (star) # (pound) 5 (five) + your 4-digit coin box amount
security code.

Verify that the voice prompt in the handset repeats "0".

Determining the Coin Box Amount

1. Lift the handset off-hook & listen for dial tone.

2. Dial * (star) # (pound) 4 (four) + your 4-digit coin box amount
security code.

The voice prompt in the handset should then prompt the current coin
box amount.

S-310 DIAGNOSTIC PROCEDURES

Use the following procedures to verify proper operation of hardware
components. If any of the diagnostic tests fail, check the Trouble-
shooting Guide for help.

Entering the Diagnostic Mode

1. Enter the program mode.

2. Dial 9 (nine) 0 (zero) 2 (two)

Performing Keypad Test

1. Make sure phone is in diagnostic mode.

2. Press each key on the keypad (except the * star key) and verify
that the voice prompt in the handset repeats each number you press.

Performing Coin Validation Test

1. Make sure phone is in diagnostic mode.

2. Deposit a quarter & verify that the voice prompt in the handset
repeats "25 cents".

3. Deposit a dime & verify that the voice prompt in the handset
repeats "10 cents".

4. Deposit a nickel & verify that the voice prompt in the handset
repeats "5 cents".

Performing Relay Refund & Collect Test

1. Make sure phone is in diagnostic mode.

2. Deposit a coin.

3. Dial * (star) 1 (one) & verify that the coin is refunded into the
coin return bucket.

4. Deposit another coin.

5. Dial * (star) 2 (two) & verify that the coin is collected into the
coin box.

Performing Battery Voltage Test

1. Exit diagnostic mode.

2. Lift receiver & listen for dial tone.

3. Dial * (star) # (pound) 67 (six, seven)

One `beep' = good battery; Two `beeps' = marginal battery; Three
`beeps' = low battery

Performing Manual Battery Charge

1. Lift receiver & listen for dial tone.

2. Dial * (star) # (pound) 68 (six, eight)

3. Listen for "Please Wait" voice prompt & then hang up. The procedure
should last approx. 2 minutes & cannot be interrupted once it has been
started.

TESTING THE LOOP CURRENT LEVEL

A minimum of 22ma (mili-amps) (or 44VDC) loop current must be provided
to the CTR-201 from the Telephone Company's Central Office. In certain
situations, due to the distance between the Central Office and the
phone site, the loop current may not meet the required level of 22ma.
If the loop current is below 22ma, dial tone may not occur or the
phone may experience only momentary burst of dial tone. If the loop
current level is below 22ma, you should contact your Local Telephone
Co.

1. Locate a test meter (multi-meter) for this task.

2. Set the meter to Amps DC.

3. Make sure the incoming Telco tip wire is connected to the terminal
block (located at the base of the lower housing.)

4. Make sure the incoming Telco ring wire is disconnected from the
terminal block.

5. Connect one lead of the meter to the disconnected Telco ring wire.

6. Disconnect the pigtail cable ring wire (red wire) from the
terminal block.

7. Connect the other lead of the meter to the disconnected pigtail
cable ring wire.

8. Lift the handset off-hook and record the loop current level shown
on the meter. Verify that the reading is greater than 22ma (mili-amps).

FCC & EQUIPMENT SPECIFICATION

FCC Registration

FCC Registration Number: F2LUSA-24605-CX-E

Ringer Equivalency Number: 0.0B

This device complies with Part 15 of the FCC Rules.
This equipment complies with Part 68 of the FCC rules.
On the Chass is bracket of this equipment is a label that contains,
among other information, the FCC Registration Number and Ringer
Equivalence Number (REN) for this equipment. If requested,
this information must be provided to the telephone company.

The REN is used to determine the quantity of the devices that may be
connected to the telephone line. Excessive REN's on the telephone line
may result in the devices not ringing in response to an incoming call.
In most but not all areas, the sum of the REN's should not exceed five
(5.0). To be certain of the number of devices that may be connected to
the line, as determined by the total REN's, contact the telephone
company to determine the maximum REN for the calling area.

For compliance with state tariffs, the telephone company must be
notified prior to connection of the equipment (S-310) to the telephone
line. In some states, approval for equipment connection must be
obtained from the Public Utility Commission, Public Service
Commission, or Corporate Commission prior to connection.

If the terminal equipment (S-310) causes harm to the telephone
network, the telephone co. will notify you in advance that temporary
discontinuance of service may be required. If advance notice is not
practical, the telephone company will notify the customer as soon as
possible. You will also be advised of your right to file a complaint
with the FCC if you believe it is necessary.

The telephone company may make changes in it's facilities, equipment,
operations, or procedures that could affect the operation of the
equipment, (S-310). In this case, the telephone company will provide
advance notification in order for you to make the necessary
modifications to maintain uninterrupted service.

This equipment is hearing aid compatible.

ETL Listing

This equipment (S-310) is in compliance with the requirements of the
Standard for Telephone Equipment (UL-1459, Second Edition). This
equipment is listed by the ETL Testing Laboratories in compliance with
the above standard.

Electrical

Input Power-------------------------------------- Line Powered, loop start

Loop Limit--------------------------------------- 22ma to 90ma

Dialing-------------------------------------------- Pulse or Touch Tone

DTMF P21:53 15/05/01ower Level (LOW Group)----------- -10.5 dBm (min) into 600 ohms

DTMF Power Level (HIGH Group)---------- -8.5 dBm (min) into 600 ohms

DTMF Power Level (per pair)----------------- +1.0 dBm (max) into 600 ohms

DTMF Frequency Tolerance------------------- + 0.5% per frequency

DTMF Twist-------------------------------------- < 3 dB

Hardware

Housing Type------------------------------------ GTE / Quadrum Style Housing)

Environmental

Temperature-------------------------------------- - 40� to +150� F (-40� to +65� C)

Humidity------------------------------------------ - 0 to 95% relative, non-condensing

W W W . N E T T W E R K E D . N E T

-
<phlux> least your girlfriend isnt saying she wants to marry you cuz shes
pregnant and needs a father to help raise her son
-

Nevada probes Vegas phone hacks
Do hackers control sin city? Adult entertainment operators, private eyes, a
bail bondsman and his bounty hunter all say they've felt the pinch from a
shady cyberpunk syndicate. Now the state has launched an investigation, and
there could be millions on the line.

By Kevin Poulsen
May 14, 2001 1:12 AM PT

Eddie Munoz knows a secret about Las Vegas.

As the operator of one of the city's oldest in-room adult entertainment
services, Munoz knows Vegas is a town fuelled by the unceasing buzz of money
and vice. When he was at the top of his game his phones rang 100 times a
day, and he dispatched private nude "dancers" (prostitution is illegal in
Las Vegas) to the hotels along the Strip fifteen to twenty times a night,
raking in, he says, $240,000 a year in referral fees.

That's not the secret.

The secret, Munoz says, lies in the hundreds of miles of modern glass fiber
and aging copper wire buried beneath the town's sun-baked streets, and in
the dozens of digital switches that speed data and voice from one end of the
Strip to the other. Munoz believes that for a decade a shadowy cabal of
criminals, corrupt insiders and professional hackers has had an illicit
stranglehold on Vegas cyberspace, and all but muscled him out of the adult
entertainment industry by selectively blocking, tapping and rerouting the
telephone lines crucial to the outcall biz.

"In this business, you receive your calls from 5:00 in the afternoon until
5:00 in the morning, and that's when they hit us," says Munoz. "It's like
you're the Maytag man. The phone will not ring."

These days Munoz is lucky if he gets one or two customers a night, and his
once great empire of vice is a threadbare operation run from an office in
his home, far from Vegas' neon core. He's hanging on primarily through his
hard-won ownership of nearly half of the five hundred licensed news racks on
the Strip, which he crams with stacks of his own paper, "The Las Vegas
Informer" -- twelve gritty pages of advertisements for "Red Hot Red Heads"
and "Hot Hot Hot Tall Sexy Blondes." Until recently, every phone number
advertised in the paper went to Munoz's switchboard, yet his phones still
didn't ring. The economics of the situation eventually forced him to sell
advertising space to a competitor to pay the rent.
Munoz believes Soranno is one of the masterminds of a plot to destroy his
business; Soranno says that's exactly the kind of talk that nearly got him
whacked.
Munoz's phone problems are legion; his log of trouble-reports stretches
longer than a junkie's rap sheet. Callers from outside Vegas, or from
payphones and cell phones, get through, he says, but hotel callers get false
busy signals, or reach silence, driving them into the arms of competing
services. Sometimes calls are rerouted directly to a competitor, he claims.
And when a would-be customer does get through, and Munoz dispatches a dancer
to the tourist's hotel room, she's likely to find another entertainer
already there. "Sometimes they beat us to the calls, like they're
listening," says Munoz.

At least three other adult entertainment outfits, a private investigator and
a bail bondsman have reported similar patterns. "I'd get half a ring, and
pick up the phone, and there would be no one there," says Hilda Brauer, the
former owner of the now-defunct "Sexy Girls" outcall service. In 1998,
Brauer filed suit against the local phone company, a competitor she blamed
for the problem, and the publisher of the Donnelly Directory, in which Sexy
Girls had seven full page ads. She later dropped the suit, closed her
business, and now makes her living telling fortunes for a psychic hotline.
"I lost my home, I had to sell my furniture to get money to move into an
apartment," says Brauer.

Peter Vilencia, a former bail bondsman, had phone problems as well. Vilencia
purchased Bail Bonds Inc. in 1996, and, after a week of brisk business
springing drunken tourists and small time crooks from the Clark County
Detention Center, he suddenly suffered a sharp drop in call volume. "At 4:00
in the afternoon Friday, my phone would stop ringing," says Vilencia, who
sold the company last year. "Almost every weekend for nearly four years, you
could set your watch by it."

Sabotage defies testing
"We would lose our phones from Friday night, through the weekend, and that's
the most common time people get arrested," recalls Mike Kapfer, Vilencia's
former bounty hunter. Sometimes the phones would half-ring, as though call
forwarding was in effect; more commonly, inmates would seem to be switched
to a competing bond writer in mid call. Only calls from the jail were at
risk. "If I tried calling the number from my cell phone, it would go
through," says Kapfer.

Both men agree with Munoz and Brauer that someone is pulling strings from
deep within the network. "I had guys watching the building in the back where
the phone lines come in, and the junction boxes down the street," says
Vilencia. "It had to be internal, nobody else had access."

But even after Brauer's lawsuit, years of formal complaints from Munoz, a
written complaint from a private investigator who claimed to be losing
calls, and two stories about the call diversion allegations in The New York
Times, the local phone company is adamant that nothing is wrong.

"We've run our tests, we've spent time and resources on this, and we haven't
seen any indication of call diversion," says Scott Collins, of Sprint
subsidiary Central Telephone's department of regulatory affairs. Last
November, at the direction of the Nevada Public Utilities Commission (PUC),
the phone company ran three days of test calls from five different Las Vegas
hotels: the Sahara, Travel Lodge, Vagabond, Motel 6, and Four Queens. Of 205
calls, all but 23 went through, and none were diverted to competitors.
(Further investigation of the 23 incomplete calls turned up innocent
explanations.) Testing by AT&T in 1997 produced similar results.

Munoz blames leaks -- he says everyone knew the tests were taking place, and
the culprits deliberately let the calls slip through. But in December, a
reporter's call from a Vegas hotel also went through without incident.

Could the Vegas cyber jacking be a myth, woven from the detritus of failed
businesses and blurry technological anecdotes? If so, it's a myth that's
attained the status of 'common knowledge' on Vegas' nocturnal fringe, and in
one bizarre case, it almost made an adult entertainment operator the victim
of brutal mob reprisal.

Vinnie "Aspirins" and his power drill
It happened in 1998: An FBI investigation into police corruption in Vegas
turned up a six-man organized crime plot to muscle in on a handful of
successful Las Vegas outcall services, which had been trouncing a mob-backed
venture headed by one of the men, Christiano DeCarlo.

According to court documents, the conspirators, allegedly affiliated with
the Gambino crime family, were particularly interesting in moving in on
Richard Soranno, the owner of one of the town's largest services, Vegas
Girls. They believed Soranno had been diverting phone calls from
competitors, including DeCarlo, with the help of a mysterious computer
expert named Charles Coveney.

"Coveney has contacts in the Sprint Telephone Company and is able to have
telephone calls diverted from one number to another," the gangsters
believed, according to an FBI affidavit. The men expected to "persuade"
Coveney to leave Seranno "and assist DeCarlo in his out call business by
diverting telephone calls to DeCarlo." Among the persuasive tools at the
gang's disposal, an enforcer named Vinnie "Aspirins" Congiusti, flown in
from Tampa, who reputedly earned his nickname by once using a cordless power
tool to drill holes in someone's head.

When the mobsters began scouring Las Vegas for Coveney, the FBI was forced
to swoop in, prematurely pulling the plug on a massive undercover operation.
All six men later plead guilty to conspiracy. Vinnie "Aspirins" died in jail
from apparent heart failure last year.

Today, there's no love lost between Munoz and Soranno; Munoz believes, but
admits he cannot prove, that Soranno is one of the masterminds of a plot to
destroy his business, while Soranno says that's exactly the kind of talk
that nearly got him whacked. "It all got started because Munoz picked up on
a rumor and made it into a thing," says Soranno. "He put my life in danger."
The sex mogul says he doesn't know anyone named Charles Coveney, and has
triumphed in the adult entertainment trade purely through marketing skill
and general business acumen. "Munoz is the worst businessman in the world,"
Soranno says. "If you were the worst businessman in the world, would you get
calls?"

Telco: Vegas is hack proof
But even Soranno sees corruption in the ebb and flow of Vegas' telephonic
tide -- though not in Sprint's network. At some hotels, he believes, corrupt
insiders monitor the PBX logs for calls to adult entertainment services.
When they spot one, they leapfrog the service by sending their own
entertainer to the guest's room. "Once they know there's an interested
party, they can send someone up," says Soranno. If true, the tactic would
explain the duplicate-dancer scenario Munoz reports. "If a girl goes to a
call, and another girl is already there, the first thing they think is
someone's tapping the phone," says Soranno.

Sprint's Collins says that, as far as Sprint Central Telephone knows, the
company has never had a problem with corrupt employees or hackers of any
kind. "No one that we're aware of," says Collins. "We haven't had any
indication that any of that has happened."

The company came to the same conclusion in September 1995, in response to a
complaint filed with the Nevada PUC (then called the Public Service
Commission) by Hilda Brauer. According to documents in the case, the
commission's staff concluded that the volume of complaints suggested
something was indeed rotten in Vegas cyberspace, but there was no "probable
cause" to believe Sprint Central Telephone was culpable. The commission
noted that the telephone company had "followed established rules and
regulations and had turned up no evidence of an illegal intrusion into its
network."

For decades, regional and long distance telephone companies from coast to
coast have seen hackers gain control of critical systems. Most recently, in
1999 federal officials won guilty pleas from three members of a nationwide
hacker group they dubbed "The Phone Masters." Until the FBI raided them in
1995, The Phone Master had access to Sprint Long Distance, Southwestern Bell
and GTE computers, and in some areas of the country were able to obtain
unlisted phone numbers, monitor phone lines, and leverage their access to
crack unrelated systems, including the FBI's National Crime Information
Center (NCIC).

If Sprint Central Telephone has never been hacked, the company is a rarity
among telecommunications carriers. But SecurityFocus has learned that the
company's Las Vegas network may not be immune to hackers after all.

"Vegas was easy"
Until he went on the lam in the early nineties, Las Vegas was a
home-away-from-home for the world's most famous hacker, Kevin Mitnick, who
had family in town. And from approximately 1992 until his February 1995
arrest, Mitnick says he enjoyed substantial illicit access to the Vegas
network. What's more, he recalls once being approached with an offer to
redirect calls from an adult entertainment service for a single weekend, for
$3,000. "They wanted me to somehow take control of the line and forward it,"
Mitnick recalls."

"It would have taken, had I wanted to do it, all of three minutes."

Currently under court supervision after five years in prison, Mitnick is not
known to have ever cashed in on his hacking, and he says he never
participated in a call diversion scheme. But he points to two specific holes
in the Las Vegas network that would make such a scheme possible for a
knowledgeable insider, or a sophisticated hacker.

For starters, Mitnick says he had direct access to the control consoles on
Vegas' switching systems through dial-up modems. Each Nortel DMS switch had
a secret phone number, and a default username and password. The dial-ups
were normally inaccessible, and Mitnick had to call a Sprint employee and
pose as a technician to get the lines turned on, he says. Once that was
done, "I had the same access to the switch that the techs did," he recalls:
total control over how calls are routed.

With access to the switches, Mitnick found it useful to launder his calls
through sin city as an anti-tracing tactic, even when he was hiding out in
Seattle and Raleigh, North Carolina, "Vegas was easy," Mitnick says.

The second hole is a testing system pronounced "Callers" -- Mitnick says he
never saw its name in print, so he doesn't know how it was spelled or
capitalized. As he describes it, the system was designed to allow phone
company workers to run tests on customer lines, "loops" in the parlance of
telephony, from a central location. The system consisted of a handful of
client computers, and remote servers attached to each of Sprint Central
Telephone's DMS-100 switches.

Vegas' remote servers were poorly protected, Mitnick says. They were
accessible through low-speed dial-up modems, guarded by a technique only
slightly more secure than simple password protection: the server required
the client -- normally a computer program -- to give the proper response to
any of 100 randomly chosen challenges. "It would prompt you with a query,
and you would have to answer promptly," Mitnick says. "It was a number, like
54, and it had a certain hex response, like 3FAE."

Mitnick says he was able to learn the Las Vegas dial-up numbers by conning
Sprint workers, and he snagged the "seed list" of challenges and responses
from the company that made the system, Ontario-based Northern Telecom,
renamed in 1999 to Nortel Networks. "I had to call Nortel and have one of
the engineer's talk me though it," says Mitnick. "I told them I was writing
software that had to interface with it."

The system allowed users to silently monitor phone lines, or originate and
answer phone calls on other people's lines, Mitnick says. "All you needed
was a laptop and a phone." The implications go well beyond mere
call-napping. "Somebody with real criminal intent, in a city like Las
Vegas-- think of the possibilities."

Nortel spokesman David Chamberlin dismissed Mitnick's account as "wild
speculation" and "rumor." But a list on the company web site offers a
feature called "CALRS", "Centralized Automated Loop Reporting System," as an
option on the company's DMS line of switches. Elsewhere on the site, Nortel
literature describes CALRS as an "external test access system."

A Sprint spokesperson, and an attorney representing the company, both
declined to comment on CALRS, and would neither confirm nor deny the
existence of a poorly protected testing system that might be an open door
into the inner sanctum of Vegas' telecommunications infrastructure.

Public hearings set
The company may not be able to stay mum forever. After fielding years of
complaints, the State of Nevada is now taking Munoz's allegations seriously.
In February, over Sprint's objections, the PUC found "probable cause" for a
full investigation, and has scheduled public hearings for September.
Meanwhile, the commission is demanding answers. Last month it formally
served Sprint with a "data request" asking, among other things, whether the
company has ever been hacked. The company responded Thursday, once again
claiming that there was no evidence that it had ever suffered from corrupt
employees or outside intruders.

Sprint's Collins is no longer talking to reporters, referring calls to the
company's outside counsel, Patrick Reilly, a lawyer with the Nevada law firm
Hale Lane Peek Dennison Howard and Anderson. "To our knowledge, there's been
no evidence of a breach of the network," says Reilly.

"Now I have subpoena power," says Munoz. "Look out."

"Eddie's been knocking on people's doors, various governmental entities, for
years, and as far as I know this is the first genuine forum that he's
gotten," says Nevada PUC consumer complaint manager Rick Hackman. "Although
he hasn't convinced us that Sprint is at fault, we believe that he deserves
the forum to make his case in front of the full commission."

The PUC decision to hold hearings is an enormous victory for Munoz, and it
raises the stakes for Sprint Central Telephone. If Munoz prevails, the
commission could impose monetary fines and sanctions. Further, Munoz says
he'll sue the company for $20 million.

That's the price, he says, for ten years of lost business, in a period
that's seen mind boggling growth in the city. Construction of super hotels
like the Bellagio, the Venetian, Paris, and Aladdin have pushed Las Vegas'
guest capacity to over 120,000 hotel rooms, and the city now hosts some four
thousand conventions each year. And that's a lot of people who could have
been trying to call one of Munoz's Hot Hot Hot Tall Sexy Blondes.

--
p1asm1c/#hackcanada think he has discovered a condition in hackers and
phreakers once they reach the age of 19. This erratic behaviour
has been displayed by the clone and wizbone

<p1asm1c> i call it haxorpause.
-

+++++++++++++++++
+Poem by wizbone+
+++++++++++++++++

This is a poem
I wrote it myself
I can't write poems
So shut the fuck up

The only reason
I wrote this poem
was so I could published
In k-line #15

So please oh please
publish me clone
because if you don't
I'll cry like a girl

-
<cyb> jesus christ.. don't you know them alabama porch monkies HATE being
called kneegrows!?
-

GUTSCI Protocol
---------------

Hello, all. This is my first contribution to this zine, and I'm
sad to say it will be, for the most part a cut-and-dry and not to interesting
article that will propose some standards for the GUTSCI protocol.

GUTSCI, or Global Underground Technology Secure Communications Infrastructure
(pronounced gut-see) was first proposed by Agent Smith in a brief
article outlining the purpose and rational behind the protocol,
without going into much (any) specifics of how the technical aspects
should work.

You should be able to find Smith's original article at nettwerked.net,
unless the link is dead.

Basically, GUTSCI is a secure chatting, instant messaging, and file
transfer protocol. It's major focus is to develop a cryptographically
secure, anonymous peer-to-peer system. That means that we can't
rely on any central server whatsoever, all communication must use
open cryptographic standards, authentication must take place peer
to peer (this should prove to be exceedingly difficult...).

Anyways, I'm sure it's obvious by now that this model poses many
obstacles, not the least of which that peer-to-peer communication
is almost unheard of because of it's difficulty in designing a reliable
secure system around it, but I wholy believe it's possible.

One last thing before I jump into the technicalities of the program,
this project will only be able to grow and develop if we get lots
of feedback, suggestions, criticism, etc.

The Protocol
------------

The entire protocol will take place over a TCP/IP network. There will
be a standard (though adjustable) port. The port has yet to be
determined. All connections will use simple BSD sockets, connect() and
whatnot. This is so we can port it to the maximum number of operating
systems possible.

People can be running 3 different services on their machine at once,
although only 1 is required, all of them having their own standard
port number.

1 --- Server
2 --- Client
3 --- Messaging

Now what's all this about server/client? I thought it was supposed to
be peer-to-peer? Is this guy on crack? Well, that's none of your
damn business. Actually, since anyone can set up any of these services
and link them together effortlessly, it will still be a peer-to-peer
system. Keep reading.

Once the server is launched (probably as a daemon, and *NOT AS ROOT*)
it will just sit there listening for open connections. It will respond
differently to each request, of course. One notable case is that it
will be able to accept connections from other servers as well as clients,
enabling a network of GUTSCI severs to build up. More later.

The client connects to the server, and can issue it various commands,
but will inevitably either have the connection terminated, or be
joined to a chat room. More later.

The messanger will maintain a connection with the server, much like
the client, but will not be joined to a chat room, it will just sit
and listen for messages off the GUTSCI network. More later.

Connection Requests
-------------------

CHAT AS <name>

-Rather simple really. A client connects to a server, and the server
connects the client to a chat room with all the other parties that
have connected to that server then sends 'Ok.'. One last note:
everything sent to the server from a client is concatenated with the
name that the client submitted on the chatting request, so here might
be a typical connection:

Client connects to server.
Client sends -> CHAT AS JimmyJazz
Client recieves <- Ok.
Client sends -> Hey guys.
Server sends out to all clients -> <JimmyJazz> Hey guys.

etc.

Note: The actual messages will be encrypted, and this will be standardized
in the client, *not* the server.

RELAY <random string of text>

-Sends another relay to all of the server's it has LATCHed onto (more later),
except the one it got the RELAY request from. The RELAY that it sends will
have the exact same string of random text as the original RELAY.

LATCH <server> [port]

-Tells the server to make an attempt to latch onto <server>. The server
would go through a couple of steps first.

The server makes a connection to <server> on the optional port [port],
And does a RELAY. It then listens for 5 seconds to see if that random
string of text gets back to it. If it doesn't, then it adds <server>
to the BOTTOM of it's list of servers to connect to. Note, the LATCH
connection will still be open, and the server will send back either:
"Ok." or "Relay loop.". If it recieves "Relay loop." it will drop the
connection. If it recieves "Ok." then it also will add the server to
the BOTTOM of it's list of servers to connect to. Note, some error
checking must be in place to prevent a server from being listed more
than once in the list. Once this latch connection is open, messages
will be sent both ways in the connection. This is how the instant
messaging feature will work.

MESSAGING AS <name>

-The server forwards all messages destined to <name> to this person, as well
as relaying them to the next server. It will also take any messages from
this connection and then send it to all of it's LATCHed connections.

As you can see, the server offers little security whatsoever. All of the
encryption will be standardized in the client. Sure, you'll be able to use
somebody elses nick, and you'll be able to recieve all of his/her messages, but
you won't have their private key so you will be unable to read it.

Also, the client will encrypt all messages in a channel, so if you don't
have the particular key that people are using on that server, you won't
be able to read what they're saying.

NC Hack: Ok, I've already released some unpolished crappy code. The worst
part is, it doesn't follow this protocol at all. Yeah, that's funny.
It doesn't support messaging, you can't specify a name, basically all that
you do is connect to the server, it sends you a port number, you connect
to that port, and anything you send will be sent to anyone else on that
server. Check out the README included with that release for more info.
I intend to write a server that fully follows this protocol eventually.

The main body of code is in the gutsec program. Basically, this program
is a piece of tubing you can put in a pipe (in unix, of course), and
if you specify the -e <key> option, it will 3DES encrypt everything
from stdin and send it to stdout. Likewise with the -d option, but it
decrypts. I also went to great lengths to make sure that only human
readable ASCII characters were transmitted through the pipe. Oh, and don't
use it for a reliable data transfer yet. It garbles about .5% of the text
you send through. Not bad, but I hope to fix this soon. Once I get all
the bugs worked out, I'm considering making a seperate program called
spipe or something.

Anyways, to be perfectly honest I'm beginning to reconsider the design
issues around GUTSCI, and I'm thinking maybe it should be either
an instant messaging protocol or a chatting protocol. Let me know what
you think.

I'm even thinking of maybe dropping this project, and working on a secure
client for IRC since IRC is already an established interface, and has
proved to be extremely popular, and difficult to shut down. Maybe even
a trusted bot that has a key from everyone, and when it gets a message,
it decrypts it, encrypts it with the destinations key and sends it to him.
Of course this raises question's like "Can I trust the bot owner?" and "Is he
logging my messages?". Maybe the bot could be a public key server. Anyways,
I'm itching to do something. Let me know what you think.

Fractal
doug@bearcountry.cjb.net (I should see if I could get @hackcanada.com...)
Fractal irc.h410g3n.com #hackcanada or #cpu (I should be running a server soon)

-
<Flopik> i can have sexual friendship with another english phreaker, i
have enought teddy bear .. sniff
-

-- Credits

Without the following contributions this zine issue would
be fairly delayed or not released, so thank you to the following people:

Cenobyte, Fractal, Kevin Poulsen, Nikola Tesla,
Nettwerked, The Clone, Wizbone, WNN

-- Shouts:

Hack Canada (#HackCanada), #CPU, #k-1ine, #altphreakingfaq

k-rad-bob @ b0g, Blackened @ Damage Inc., The Grasshopper Unit,
Flippersmack, Pyrofreak, _plappy, soap, and lastly to everyone
and anyone who contributes to the Canadian H/P scene.

;. .;.. ; ;. ;..
;.. .;..; .;.; .;; ;..
.;..;. .;..; .;.;...; ;..;..
.;. A .;. .;.
;.. N E T T W E R K E D ;..
;..;.. P R O D U C T ;..;..
.;..; ;..;..
; .;..;.;.. .; . .;. ..;..
.;.. . .; ..;..;..;.. .;
;..;. .;.. . .;.. .;.;.
..;. ..;.. .;. ;.;..;;..;.;
;.;;..;.. ;.;.; .; .
;.;..;. .;. ;.;:.;.
,;....;.
.;.;. .;.;
.;.;.;
.;.;
;..;.
.;.;;.; .;. ..; ;. > > > WE DON'T FUCK AROUND!