no need for recursive removal of a single file

[monkeysphere.git] / website / index.mdwn

diff --git a/website/index.mdwn b/website/index.mdwn
index a7d074e4445eabfd0000ef6c588eaa9c4d680ebe..ba121a24891509bd30546d629f286033e1b9de10 100644 (file)
--- a/website/index.mdwn
+++ b/website/index.mdwn
@@ -1,3 +1,9 @@
+[[meta title="The Monkeysphere Project"]]
+[[meta license="Unless otherwise noted, all content on this web site is licensed under the GPL version 3 or later"]]
+[[meta copyright="All content on this web site is copyright by the author of that content. [Look in the revision control system](community) for details about who authored a particular piece of content."]]
+
+# The Monkeysphere Project #
+
 The Monkeysphere project's goal is to extend OpenPGP's web of trust to
 new areas of the Internet to help us securely identify each other
 while we work online.
@@ -19,8 +25,8 @@ the first time you log in to a new server, asking if you want to trust
 the server's key by verifying the key fingerprint.  Unfortunately,
 unless you have access to the server's key fingerprint through a
 secure out-of-band channel, there is no way to verify that the
-fingerprint you are presented with is in fact that of the server your
-really trying to connect to.
+fingerprint you are presented with is in fact that of the server
+you're really trying to connect to.
 
 Many users also take advantage of OpenSSH's ability to use RSA or DSA
 keys for authenticating to a server (known as
@@ -42,7 +48,7 @@ expected.
 The basic idea of the Monkeysphere is to create a framework that uses
 [GnuPG](http://www.gnupg.org/)'s keyring manipulation capabilities and
 public keyserver communication to manage the keys that OpenSSH uses
-for connection authentication.  
+for connection authentication.
 
 The Monkeysphere therefore provides an effective PKI for OpenSSH,
 including the possibility for key transitions, transitive
@@ -55,22 +61,21 @@ Under the Monkeysphere, both parties to an OpenSSH connection (client
 and server) explicitly designate who they trust to certify the
 identity of the other party.  These trust designations are explicitly
 indicated with traditional GPG keyring trust models.  Monkeysphere
-then manages the keys in the `known_hosts` and `authorized_keys`
-files directly, in such a way that is completely transparent to SSH.
-No modification is made to the SSH protocol on the wire (it continues
-to use raw RSA public keys), and no modification is needed to the
-OpenSSH software.
+then manages the keys in the `known_hosts` and `authorized_keys` files
+directly, in such a way that is completely transparent to `ssh`.  No
+modification is made to the SSH protocol on the wire (it continues to
+use raw RSA public keys), and no modification is needed to the OpenSSH
+software.
 
 To emphasize: ***no modifications to SSH are required to use the
 Monkeysphere***.  OpenSSH can be used as is; completely unpatched and
 "out of the box".
 
-## Links ##
+## License ##
 
-* [OpenSSH](http://openssh.com/)
-* [GnuPG](http://www.gnupg.org/)
-* [Secure Shell Authentication Protocol RFC 4252](http://tools.ietf.org/html/rfc4252)
-* [OpenPGP RFC 4880](http://tools.ietf.org/html/rfc4880)
+All Monkeysphere software is copyright, 2007, by [the
+authors](community), and released under [GPL, version 3 or
+later](http://www.gnu.org/licenses/gpl-3.0.html).
 
 ----