aboutsummaryrefslogtreecommitdiff
path: root/openssl/README
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2006-08-01 08:12:00 +0000
committerRob Austein <sra@hactrn.net>2006-08-01 08:12:00 +0000
commit6cdb33c8724a65d07c4d459d5525b1ffec860f33 (patch)
tree5b7d254de3f63117675fa1a21607ec805342e0d2 /openssl/README
parent74355231cb3896ba612979427e2b9dec5b581b05 (diff)
update notes
svn path=/openssl/README; revision=124
Diffstat (limited to 'openssl/README')
-rw-r--r--openssl/README9
1 files changed, 8 insertions, 1 deletions
diff --git a/openssl/README b/openssl/README
index 88ec7563..842247d1 100644
--- a/openssl/README
+++ b/openssl/README
@@ -239,4 +239,11 @@ Random reminders and notes to myself:
crypto/x509/x509_vrfy.[ch] in general are interesting.
- Need to add NIDs for RFC 3779 extensions to supported_nids[] in
- crypto/x509v3/v3_purp.c?
+ crypto/x509v3/v3_purp.c.
+
+- Initial path checking code written, but need to rewrite error
+ handling to use ctx->verify_cb(), etc.
+
+- Should we check entire chain or only up to ctx->last_untrusted? For
+ the moment I'm checking the entire chain because that's more likely
+ to yield a correct answer, albiet perhaps inefficiently.