summaryrefslogtreecommitdiffhomepage
path: root/debian
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2016-10-22 17:42:20 -0700
committerSean Whitton <spwhitton@spwhitton.name>2016-10-22 17:42:20 -0700
commit1568abf3be91aeeef298a0878bed8c784792bf6b (patch)
treef7a6853db6bbd7722e523c8caaab9a61924ba483 /debian
parentd74d6e8ff464cd22a7990adc9b44eec41bd28489 (diff)
downloadkeysafe-1568abf3be91aeeef298a0878bed8c784792bf6b.tar.gz
comment
Diffstat (limited to 'debian')
-rwxr-xr-xdebian/keysafe-server.postrm4
1 files changed, 3 insertions, 1 deletions
diff --git a/debian/keysafe-server.postrm b/debian/keysafe-server.postrm
index 8f153d4..7b8c8ca 100755
--- a/debian/keysafe-server.postrm
+++ b/debian/keysafe-server.postrm
@@ -8,7 +8,9 @@ set -e
# For the time being, at the request of upstream, we don't ever delete
# /var/lib/keysafe, even on a purge (note that for security this
-# requires that we also never delete the _keysafe user and group)
+# requires that we also never delete the _keysafe user and group). It
+# might be worth revisiting this when it is time to upload keysafe to
+# unstable -- how much is a purge meant to purge?
# Deleting this data has the potential to destroy the backups of
# people's private keys, so it probably shouldn't ever happen