The Anarchist Cookbook (42 page)
NOTE: The Ultrix mail system is extremely flexible; it is almost completely configurable
by the customer. While this is valuable to customers, it makes it very difficult to write
global instructions for the use of Ultrix mailers, because it is possible that the local
changes have produced something quite unlike the vendor-delivered mailer. One of the
popular changes is to tinker with the meaning of quote characters (") in Ultrix addresses.
Some systems consider that these two addresses are the same:
and
"site1!site2!user"@host.dec.com
while others are configured so that one form will work and the other will not. All of these
examples use the quotes. If you have trouble getting the examples to work, please try
them again without the quotes. Perhaps your Ultrix system is interpreting the quotes
differently.
If your Ultrix system has an IP link to Palo Alto (type "/etc/ping decwrl.dec.com" to find
out if it does), then you can route your mail to the gateway via IP. This has the advantage
that your Ultrix mail headers will reach the gateway directly, instead of being translated
into DECNET mail headers and then back into Ultrix at the other end. Do this as follows:
To: "alien!address"@decwrl.dec.com
The quotes are necessary only if the alien address contains a ! character, but they don't
hurt if you use them unnecessarily. If the alien address contains an "@" character, you will
need to change it into a "%" character. For example, to send via IP to [email protected], you
should address the mail.
To: "joe%widget.org"@decwrl.dec.com
If your Ultrix system has only a DECNET link to Palo Alto, then you should address mail in
much the same way that VMS users do, save that you should not put the nm% in front of
the address:
To: DECWRL::"strange!foreign!address"
Here are some typical outgoing mail addresses as used from an Ultrix system that has IP
access. Ultrix systems without IP access should use the same syntax as VMS users,
except that the nm% at the front of the address should not be used.
To: "lll-winken!netsys!phrack"@decwrl.dec.com
To: "postmaster%msp.pnet.sc.edu"@decwrl.dec.com
To: "phrackserv%CUNYVM.bitnet"@decwrl.dec.com
To: "netsys!phrack%uunet.uu.net"@decwrl.dec.com
To: "[email protected]"@decwrl.dec.com
DETAILS OF USING OTHER NETWORKS
All of the world's computer networks are connected together, more or less, so it is hard to
draw exact boundaries between them. Precisely where the internet ends and UUCP begins
is a matter of interpretation.
For purposes of sending mail, though, it is convenient to divide the network universe into
these categories:
Easynet:
Digital's internal DECNET network. Characterized by addresses of the form
NODE::USER. Easynet can be used for commercial purposes.
Internet:
A collection of networks including the old ARPAnet, the NSFnet, the CSnet, and
others. Most international research, development, and educational organizations
are connected in some fashion to the Internet. Characterized by addresses of the
form [email protected]. The internet itself cannot be used for
commercial purposes.
UUCP:
A very primitive network with no management, built with auto-dialers phoning one
computer from another. Characterized by addresses of the form place1!place2!
user. The UUCP network can be used for commercial purposes provided that none
of the sites through which the message is routed objects to that.
USENET:
Not a network at all, but a layer of software built on top of UUCP and Internet.
BITNET:
An IBM-based network linking primarily educational sites. Digital users can send to
BITNET as if it were part of internet, but BITNET users need special instructions
for reversing the process. BITNET cannot be used for commercial purposes.
Fidonet:
A network of personal computers. I am unsure of the status of using Fidonet for
commercial purposes, nor am I sure of its efficacy.
DOMAINS AND DOMAIN ADDRESSING
There is a particular network called "the Internet;" it is somewhat related to what used to
be "the ARPAnet." The Internet style of addressing is flexible enough that people use it
for addressing other networks as well, with the result that it is quite difficult to look at
an address and tell just what network it is likely to traverse. But the phrase "Internet
address" does not mean "mail address of some computer on the Internet" but rather "mail
address in the style used by the Internet." Terminology is even further confused because
the word "address" means one thing to people who build networks and something entirely
different to people who use them. In this file an "address" is something like
"[email protected]" and not "192.1.24.177" (which is what network engineers would call
an "internet address").
The Internet naming scheme uses hierarchical domains, which despite their title are just a
bookkeeping trick. It doesn't really matter whether you say NODE: :USER or
USER@NODE, but what happens when you connect two companies' networks together and
they both have a node ANCHOR?? You must, somehow, specify which ANCHOR you mean.
You could say ANCHOR.DEC::USER or DEC.ANCHOR::USER or [email protected] or
[email protected]. The Internet convention is to say [email protected], with the
owner (DEC) after the name (ANCHOR).
But there could be several different organizations named DEC. You could have Digital
Equipment Corporation or Down East College or Disabled Education Committee. The
technique that the Internet scheme uses to resolve conflicts like this is to have
hierarchical domains. A normal domain isn't DEC or STANFORD, but DEC.COM
(commercial) and STANFORD.EDU (educational). These domains can be further divided
into ZK3.DEC.COM or CS.STANFORD.EDU. This doesn't resolve conflicts completely,
though: both Central Michigan University and Carnegie-Mellon University could claim to be
CMU.EDU. The rule is that the owner of the EDU domain gets to decide, just as the owner
of the CMU.EDU gets to decide whether the Electrical Engineering department or the
Elementary Education department gets subdomain EE.CMU.EDU.
The domain scheme, while not perfect, is completely extensible. If you have two addresses
that can potentially conflict, you can suffix some domain to the end of them, thereby
making, say, decwrl.UUCP be somehow different from DECWRL.ENET.
DECWRL's entire mail system is organized according to Internet domains, and in fact we
handle all mail internally as if it were Internet mail. Incoming mail is converted into
Internet mail, and then routed to the appropriate domain; if that domain requires some
conversion, then the mail is converted to the requirements of the outbound domain as it
passes through the gateway. For example, they put Easynet mail into the domain ENE.
On a side note, the recent book The Cuckoo's Egg provides some interesting information
(in the form of a story, however) on a Tymnet hacker. Remember that he was into BIG
things, and hence he was cracked down upon. If you keep a low profile, networks should
provide a good access method.
If you can find a system that is connected to the Internet that you can get on from
Tymnet, you are doing well.
Username@f
In other words, if I wanted to mail to Silicon Swindler at 1:135/5, the address would be
[email protected] and, provided that your mailer knows the .ifna.org
domain, it should get through alright. Apparently, as of the writing of this article, they
have implemented a new gateway name called fidonet.org which should work in place of
ifna.org in all routings. If your mailer does not know either of these domains, use the above
routing but replace the first "@" with a "%" and then afterwards, use either of the
following mailers after the "@": CS.ORST.EDU or K9.CS.ORST.EDU (i.e. username%f
#>.n
K9.CS.ORST.EDU]).
The following is a list compiled by Bill Fenner ([email protected]) that was posted on
INFONETS DIGEST which lists a number of FIDONET gateways:
NetNodeNode
Name
10456milehi.ifna.org10555casper.ifna.org107320rubbs.ifna.org109661blkcat.ifna.org1
25406fidogate.ifna.org12819hipshk.ifna.org12965insight.ifna.org143N/Afidogate.ifna.org1
52200castle.ifna.org161N/Afidogate.ifna.org36917megasys.ifna.org
NOTE: The UUCP equivalent node name is the first part of the node name. In other
words, the UUCP node milehi is listed as milehi.ifna.org but can be mailed directly over the
UUCP network.
Another way to mail to FIDONET, specifically for Internet people, is in this format:
ihnp4!necntc!ncoast!ohiont!
And for those UUCP mailing people out there, just use the path described and ignore the
@husc5.harvard.edu portion. There is a FIDONET NODELIST available on most any
FIDONET bulletin board, but it is quite large.
ONTYME
Previously known as Tymnet, OnTyme is the McDonnell Douglas revision. After they bought
out Tymnet, they renamed the company and opened an experimental Internet gateway at
ONTYME.TYMNET.COM but this is supposedly only good for certain corporate addresses
within McDonnell Douglas and Tymnet, not their customers. The userid format is xx.yyy or
xx.y/yy where xx is a net name and yyy (or y/yy) is a true username. If you cannot directly
nail this, try:
xx.yyy%ONTYME.TYM
130.Sodium Chlorate by the Jolly Roger
Sodium Chlorate is a strong oxidizer used in the manufacture of explosives. It can be used
in place of Potassium Chlorate.
Material Required:
2 carbon or lead rods (1 in. diameter by 5 in. long)
Salt, or ocean water
Sulfuric acid, diluted
Motor Vehicle
Water
2 wires, 16 gauge (3/64 in. diameter approx.), 6 ft. long, insulated.
Gasoline
1 gallon glass jar, wide mouth (5 in. diameter by 6 in. high approx.)
Sticks
String
Teaspoon
Trays
Cup
Heavy cloth
Knife
Large flat pan or tray
Sources of Carbon or Lead rods:
Dry Cell Batteries (2-« in. diameter by 7" long) or plumbing supply store.
Sources of Salt Water:
Grocery store or ocean
Sources of Sulfuric Acid:
Motor Vehicle Batteries.
Procedure:
Mix « cup of salt into the one gallon glass jar with 3 liters (3 quarts) of water.
Add 2 teaspoons of battery acid to the solution and stir vigorously for 5 minutes.
Strip about 4 inches of insulation from both ends of the two wires.
With knife and sticks, shape 2 strips of wood 1 by 1/8 by 1-«. Tie the wood strips to the
lead or carbon rods so that they are 1-« inches apart.
Connect the rods to the battery in a motor vehicle with the insulated wire.
Submerge 4-« inches of the rods in the salt water solution.
With gear in neutral position, start the vehicle engine. Depress the accelerator approx. 1/5
of its full travel.
Run the engine with the accelerator in this position for 2 hours, then shut it down for 2
hours.
Repeat this cycle for a total of 64 hours while maintaining the level of the acid-salt water
solution in the glass jar.
CAUTION: This arrangement employs voltages which can be quite dangerous!
Do not touch bare wire leads while engine is running!!
Shut off the engine. Remove the rods from the glass jar and disconnect wire leads from
the battery.
Filter the solution through the heavy cloth into a flat pan or tray, leaving the sediment at
the bottom of the glass jar.
Allow the water in the filtered solution to evaporate at room temperature (approx. 16
hours). The residue is approximately 60% or more sodium chlorate which is pure enough
to be used as an explosive ingredient.
131.Mercury Fulminate by the Jolly Roger
Mercury Fulminate is used as a primary explosive in the fabrication of detonators. It is to
be used with a booster explosive such as picric acid or RDX (which are elsewhere in this
Cookbook).
Material Required:
Nitric Acid, 90% conc. (1.48 sp. gr)
Mercury
Ethyl (grain) alcohol (90%)
Filtering material [Paper Towels]
Teaspoon measure (¬, «, and 1 tsp. capacity)-aluminum, stainless steel or wax coated
Heat Source
Clean wooden stick
Clean water
Glass containers
Tape