=== modified file 'Makefile'
--- Makefile	2008-09-12 19:12:40 +0000
+++ Makefile	2008-09-13 15:36:18 +0000
@@ -172,7 +172,7 @@
 		$(PREFIX)/lib/mandos/plugins.d
 	if [ "$(CONFDIR)" != "$(PREFIX)/lib/mandos" ]; then \
 		install --mode=u=rwx \
-			--directory "$(CONFDIR)/plugins.d"; \
+			--directory "$(CONFDIR)/plugins.d" && \
 		install --mode=u=rw,go=r etc-plugins.d-README \
 			$(CONFDIR)/plugins.d/README ; \
 	fi

=== modified file 'README'
--- README	2008-09-05 07:11:24 +0000
+++ README	2008-09-13 15:36:18 +0000
@@ -3,15 +3,15 @@
 * Mandos
   - Have your cake and eat it too!
   
-  You know how it is.  You've heard of it happening.  The Man comes
-  and takes away your servers, your friends' servers, the servers of
+  You know how it is.  You’ve heard of it happening.  The Man comes
+  and takes away your servers, your friends’ servers, the servers of
   everybody in the same hosting facility. The servers of their
-  neighbors, and their neighbors' friends.  The servers of people who
-  owe them money.  And like *that*, they're gone.  And you doubt
-  you'll ever see them again.
+  neighbors, and their neighbors’ friends.  The servers of people who
+  owe them money.  And like *that*, they’re gone.  And you doubt
+  you’ll ever see them again.
   
   That is why your servers have encrypted root file systems.  However,
-  there's a downside.  There's no going around it: rebooting is a
+  there’s a downside.  There’s no going around it: rebooting is a
   pain.  Dragging out that rarely-used keyboard and screen and
   unraveling cables behind your servers to plug them in to type in
   that password is messy, especially if you have many servers.  There
@@ -23,7 +23,7 @@
   have to be on hand and manually type in the password at boot time.
   Otherwise the server just sits there, waiting for a password.
   
-  Wouldn't it be great if you could have the security of encrypted
+  Wouldn’t it be great if you could have the security of encrypted
   root file systems and still have servers that could boot up
   automatically if there was a short power outage while you were
   asleep?  That you could reboot at will, without having someone run
@@ -129,3 +129,24 @@
   focused, and competent attacks, but against the early morning knock
   on your door and the sudden absence of all the servers in your
   server room.  Which it does nicely.
+
+* Copyright
+
+    Copyright (C) 2008 Teddy Hogeborn
+                  2008 Björn Påhlsson
+
+** License:
+
+   This program is free software: you can redistribute it and/or
+   modify it under the terms of the GNU General Public License as
+   published by the Free Software Foundation, either version 3 of the
+   License, or (at your option) any later version.
+
+   This program is distributed in the hope that it will be useful, but
+   WITHOUT ANY WARRANTY; without even the implied warranty of
+   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
+   General Public License for more details.
+
+   You should have received a copy of the GNU General Public License
+   along with this program.  If not, see
+   <http://www.gnu.org/licenses/>.

=== modified file 'TODO'
--- TODO	2008-09-12 19:12:40 +0000
+++ TODO	2008-09-13 15:36:18 +0000
@@ -67,9 +67,7 @@
 * TODO Web site
 
 * Mailing list
-** TODO mandos-dev
-*** TODO http://gmane.org/subscribe.php
-** TODO mandos-user
+** DONE mandos-dev
 *** TODO http://gmane.org/subscribe.php
 
 * TODO Announce project on news

=== removed directory 'debian'
=== modified file 'overview.xml'
--- overview.xml	2008-09-12 19:12:40 +0000
+++ overview.xml	2008-09-13 15:36:18 +0000
@@ -6,10 +6,12 @@
   encrypted root file systems and at the same time be capable of
   remote and/or unattended reboots.  The computers run a small client
   program in the initial <acronym>RAM</acronym> disk environment which
-  will communicate with a server over a network.  The clients are
-  identified by the server using an OpenPGP key; each client has one
-  unique to it.  The server sends the clients an encrypted password.
-  The encrypted password is decrypted by the clients using the same
-  OpenPGP key, and the password is then used to unlock the root file
-  system, whereupon the computers can continue booting normally.
+  will communicate with a server over a network.  All network
+  communication is encrypted using <acronym>TLS</acronym>.  The
+  clients are identified by the server using an OpenPGP key; each
+  client has one unique to it.  The server sends the clients an
+  encrypted password.  The encrypted password is decrypted by the
+  clients using the same OpenPGP key, and the password is then used to
+  unlock the root file system, whereupon the computers can continue
+  booting normally.
 </para>