uucp_site/faq.html

83 lines
4.8 KiB
HTML

<!DOCTYPE html>
<head>
<title>Dataforge UUCP</title>
<link rel="stylesheet" href="css/main.css" type="text/css">
</head>
<body>
<div id="container">
<div id="header">
<h1>Dataforge UUCP</h1>
</div>
<div id="nav">
<ul class="menu">
<li><a href="about.html">About Dataforge</a></li>
<li><a href="manifesto.html">UUCP Manifesto</a></li>
<li><a href="sites.html">Network Sites</a></li>
<li><a href="http://uucp.dataforge.tk/~uucp/wiki/">Wiki</a><li>
<li><div style="color: green"><a href="faq.html">FAQ</a></div></li>
</ul>
<center>
<hr class="join">
<h3><a href="join.html">Join Us!</a></h3>
</center>
</div>
<div id="content">
<h3>Frequently Asked Questions</h3>
<b><i><u>Why UUCP?</u></i></b>
<br>
UUCP has a great many virtues not found in other technologies such as rsync or scp. Transmission is asynchronous due to the
bidirectional nature of links between UUCP sites. If changes are made on one site, those changes are replicated to participating
sites with no intervention by an administrator. Additionally, sending data to remote systems does not require the sending system
to know anything about the receiving end or network topology. Only a bang path is needed for transmission. Transmissions are done in batches, which makes
the protocol very efficient over unreliable or slow links (ie; dial-up, satellite, 3G, etc). UUCP also merges diffs between files with
no intervention, which makes it useful for distributing items such as news where others may frequently modify items. Unlike rsync or
scp, there is no need for a central authority. Which makes UUCP truly distributed and decentralized.
<br>
<br>
<b><i><u>Is UUCP secure?</u></i></b>
<br>
Modern implementations of UUCP, such as Taylor UUCP, are very secure. On this UUCP network, transmissions are delivered over SSH,
however, given the link agnosticism of UUCP, it could easily be sent over SSL or TLS. Authentication to the network occurs twice.
First by SSH key exchange, and second by UUCP authentication. Additionally, each piece of data sent across the wire is GPG signed
for integrity and proof of ownership. Since there is only one point of entry into the network, that greatly decreases its risk spread.
Users can do whatever they please and the rest of the network won't be compromised. Additionally, UUCP is very verbose with its logging,
which makes the protocol easily auditable.
<br>
<br>
<b><i><u>Why doesn't this have a proper name?</u></i></b>
<br>
Following past traditions of UUCP networks, the network at large has no real name. A name implies ownership, and nobody <i>owns</i> the network. Individual site
networks are free to have a proper name, but the larger network doesn't. Just as the Internet doesn't have a real name.
<br>
<br>
<b><i><u>Is this just a Linux thing?</u></i></b>
<br>
NO! WHile the named Unix-to-Unix Copy suggests being a *nix only techology, implementations exists for non-unix systems, such as VMS,
OS/2, z/OS, Windows and others. The UUCP code base is very portable and can be ran on a variety of operating systems and architectures.
Everything from a PDP-11 to a giant mainframe.
<br>
<br>
<b><i><u>Can anyone join?</u></i></b>
<br>
YES! :D While having your own UUCP presense is not required, if you are an end-user, you can peer with any number of Tier 1 hosts.
Tier 1 status is reserved for dedicated points-of-presents (see <a href="tier1.html">Tier 1</a> article)
<br>
<br>
<b><i><u>It's link agnostic? Can I run it over tin cans and string?</u></i></b>
<br>
You can peer with another UUCP site using any means of communication you wish. Whether that is a ham link, 3G, satellite, or
even dialup. UUCP does not care about the medium in which it uses.
<br>
<br>
<b><i><u>What happens if I try to lick it?</u></i></b>
<br>
You'll feel a beautiful euphoria not previously known to man
<br>
<br>
<b><i><u>How do I join?</u></i></b>
<br>
Simply go to the join page and follow it's instructions. Select whether you wish to be a Tier 1 server, or a leaf node.
</div>
</div>
</body>