# 
# patch "ChangeLog"
#  from [094cd44781ea02f96dc726319f39f89a932e69a2]
#    to [181287bddd749618979457d9b21a322a97aef769]
# 
# patch "commands.cc"
#  from [e24b9d3f4cf1db10ea68ce3733c1a8bdafb5371d]
#    to [e351cc76be3dbe3eaa3d9a35f69a3efe5b09c414]
# 
# patch "monotone.texi"
#  from [412d8c60e2a7e06ae07a6b8350393421d7f87b2b]
#    to [939f56de6aac68a630492031939ce4654f093203]
# 
--- ChangeLog
+++ ChangeLog
@@ -1,5 +1,11 @@
 2005-04-17  Matt Johnston  <address@hidden>
 
+	* commands.cc: warn that dropkey won't truly erase the privkey
+	from the database
+	* monotone.texi: same
+
+2005-04-17  Matt Johnston  <address@hidden>
+
 	* database.cc: mention that it could be the filesystem that
 	is full in the SQLITE_FULL error message
 
--- commands.cc
+++ commands.cc
@@ -1184,7 +1184,10 @@
 
   if (app.db.private_key_exists(ident))
     {
-      P(F("dropping private key '%s' from database\n") % ident);
+      P(F("dropping private key '%s' from database\n\n") % ident);
+      W(F("the private key data may not have been erased from the"));
+      W(F("database. it is recommended that you use 'db dump' and"));
+      W(F("'db load' to be sure."));
       app.db.delete_private_key(ident);
       key_deleted = true;
     }
--- monotone.texi
+++ monotone.texi
@@ -3813,7 +3813,10 @@
 This command drops the public and/or private key. If both exist, both
 are dropped, if only one exists, it is dropped. This command should
 be used with caution as changes are irreversible without a backup of
-the key(s) that were dropped.
+the key(s) that were dropped. Note also that the private key is not
+guaranteed to actually be erased from your database file - if you are
+going to make the database file public, you should use 'db dump'
+and 'db load' to import into a fresh database.
 
 @item monotone chkeypass @var{id}