diff options
| author | Rob Austein <sra@hactrn.net> | 2007-11-16 02:27:24 +0000 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2007-11-16 02:27:24 +0000 |
| commit | 59ac4ae2a536c7c4ed4425132c0adaac3e147e33 (patch) | |
| tree | 48fb1c03cf97869d051313f45711fcc4ac6074b5 | |
| parent | 6cf3c5cfc5be825f78a984dafd9f29ed7188e75f (diff) | |
Notes on expiration
svn path=/scripts/README; revision=1300
| -rw-r--r-- | scripts/README | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/scripts/README b/scripts/README index d06dcc67..c19ef380 100644 --- a/scripts/README +++ b/scripts/README @@ -53,6 +53,11 @@ pure Python and only 2% about any kind of crypto. Current TO DO list: +- Client side of expiration: how do we decide when to ask for a new + cert from our parent? Tunable (preference, if so)? Waiting for + the old one to die is not good. Reissue automatically when IRDB + valid_until changes? + - Parent side of revocation (child_cert objects) and CRL generation implemented but not yet tested. |