summaryrefslogtreecommitdiff
path: root/hurd/ng/usecaseprivatekeys.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2007-09-04 15:01:35 +0200
committerThomas Schwinge <tschwinge@gnu.org>2007-09-04 15:01:35 +0200
commitebf5adb8e9ef993d74fe61fd33c2062e7bcad1c2 (patch)
treea5063fe9d0f4c5087acb3e7bb6a007dbe86081ed /hurd/ng/usecaseprivatekeys.mdwn
parentc37a846d135125df9d9be256e62c1e8763d42fc8 (diff)
Move `NextHurd' (and everything below) into `hurd/ng'.
Diffstat (limited to 'hurd/ng/usecaseprivatekeys.mdwn')
-rw-r--r--hurd/ng/usecaseprivatekeys.mdwn13
1 files changed, 13 insertions, 0 deletions
diff --git a/hurd/ng/usecaseprivatekeys.mdwn b/hurd/ng/usecaseprivatekeys.mdwn
new file mode 100644
index 00000000..612a8f25
--- /dev/null
+++ b/hurd/ng/usecaseprivatekeys.mdwn
@@ -0,0 +1,13 @@
+_Private Keys_ as used by SSH servers, clients and generally by any cryptographic software need to be stored and manipulated securely. These may get replaced with smartcards soon, but in the mean time it appears to be an interesting use case.
+
+All Unix systems that I am aware of do not allow secrets to be protected in a manner that I would feel is appropiate. A users compromised web browser could either read your private key file or talk to the very popular ssh-agent program and get your secrets out (not sure how popular distributions are configured, but it can be done).
+
+The requirements so far are:
+
+* The secrets should not be available to general programs
+* The ability to use secrets for their intended purpose (signing/encryption/decryption/ssl streams)
+* Programs using decrypted data should be, by default, confined so that the data can't escape
+* Must be able to backupand restore secrets securely
+* Upgrading the agent software must be possible! using the backup/restore mechanism?
+
+-- [[Main/SamMason]] - 11 Jan 2007