1. 09 12月, 2000 1 次提交
    • D
      · 9d6b1ce6
      Dr. Stephen Henson 提交于
      Merge from the ASN1 branch of new ASN1 code
      to main trunk.
      
      Lets see if the makes it to openssl-cvs :-)
      9d6b1ce6
  2. 13 11月, 2000 1 次提交
  3. 27 10月, 2000 1 次提交
  4. 15 10月, 2000 1 次提交
  5. 06 10月, 2000 1 次提交
  6. 25 9月, 2000 1 次提交
  7. 18 9月, 2000 1 次提交
  8. 10 9月, 2000 1 次提交
  9. 07 9月, 2000 1 次提交
  10. 06 9月, 2000 1 次提交
    • D
      *BIG* verify code reorganisation. · 2f043896
      Dr. Stephen Henson 提交于
      The old code was painfully primitive and couldn't handle
      distinct certificates using the same subject name.
      
      The new code performs several tests on a candidate issuer
      certificate based on certificate extensions.
      
      It also adds several callbacks to X509_VERIFY_CTX so its
      behaviour can be customised.
      
      Unfortunately some hackery was needed to persuade X509_STORE
      to tolerate this. This should go away when X509_STORE is
      replaced, sometime...
      
      This must have broken something though :-(
      2f043896
  11. 14 8月, 2000 1 次提交
  12. 05 7月, 2000 1 次提交
    • R
      I got sick and tired of having to keep track of NIDs when such a thing · c2bbf9cf
      Richard Levitte 提交于
      could be done automagically, much like the numbering in libeay.num and
      ssleay.num.  The solution works as follows:
      
        - New object identifiers are inserted in objects.txt, following the
          syntax given in objects.README.
        - objects.pl is used to process obj_mac.num and create a new
          obj_mac.h.
        - obj_dat.pl is used to create a new obj_dat.h, using the data in
          obj_mac.h.
      
      This is currently kind of a hack, and the perl code in objects.pl
      isn't very elegant, but it works as I intended.  The simplest way to
      check that it worked correctly is to look in obj_dat.h and check the
      array nid_objs and make sure the objects haven't moved around (this is
      important!).  Additions are OK, as well as consistent name changes.
      c2bbf9cf
  13. 03 7月, 2000 1 次提交
  14. 17 6月, 2000 1 次提交
    • D
      Safe stack reorganisation in terms of function casts. · 3aceb94b
      Dr. Stephen Henson 提交于
      After some messing around this seems to work but needs
      a few more tests. Working out the syntax for sk_set_cmp_func()
      (cast it to a function that itself returns a function pointer)
      was painful :-(
      
      Needs some testing to see what other compilers think of this
      syntax.
      
      Also needs similar stuff for ASN1_SET_OF etc etc.
      3aceb94b
  15. 13 6月, 2000 1 次提交
  16. 11 6月, 2000 1 次提交
  17. 02 6月, 2000 1 次提交
    • R
      There have been a number of complaints from a number of sources that names · 26a3a48d
      Richard Levitte 提交于
      like Malloc, Realloc and especially Free conflict with already existing names
      on some operating systems or other packages.  That is reason enough to change
      the names of the OpenSSL memory allocation macros to something that has a
      better chance of being unique, like prepending them with OPENSSL_.
      
      This change includes all the name changes needed throughout all C files.
      26a3a48d
  18. 01 6月, 2000 2 次提交
    • G
      "make update" + stripping the type-specific stack functions out of · 7edd2091
      Geoff Thorpe 提交于
      libeay.num and ssleay.num.
      7edd2091
    • G
      The previous commit to crypto/stack/*.[ch] pulled the type-safety strings · ccd86b68
      Geoff Thorpe 提交于
      yet tighter, and also put some heat on the rest of the library by
      insisting (correctly) that compare callbacks used in stacks are prototyped
      with "const" parameters. This has led to a depth-first explosion of
      compiler warnings in the code where 1 constification has led to 3 or 4
      more. Fortunately these have all been resolved to completion and the code
      seems cleaner as a result - in particular many of the _cmp() functions
      should have been prototyped with "const"s, and now are. There was one
      little problem however;
      
      X509_cmp() should by rights compare "const X509 *" pointers, and it is now
      declared as such. However, it's internal workings can involve
      recalculating hash values and extensions if they have not already been
      setup. Someone with a more intricate understanding of the flow control of
      X509 might be able to tighten this up, but for now - this seemed the
      obvious place to stop the "depth-first" constification of the code by
      using an evil cast (they have migrated all the way here from safestack.h).
      
      Fortunately, this is the only place in the code where this was required
      to complete these type-safety changes, and it's reasonably clear and
      commented, and seemed the least unacceptable of the options. Trying to
      take the constification further ends up exploding out considerably, and
      indeed leads directly into generalised ASN functions which are not likely
      to cooperate well with this.
      ccd86b68
  19. 17 5月, 2000 2 次提交
  20. 16 5月, 2000 1 次提交
  21. 05 5月, 2000 1 次提交
  22. 02 5月, 2000 1 次提交
  23. 09 4月, 2000 1 次提交
  24. 26 3月, 2000 1 次提交
  25. 07 3月, 2000 1 次提交
  26. 05 3月, 2000 1 次提交
  27. 26 2月, 2000 2 次提交
  28. 13 2月, 2000 1 次提交
  29. 11 2月, 2000 1 次提交
  30. 07 2月, 2000 1 次提交
  31. 01 2月, 2000 1 次提交
    • U
      EBCDIC support. · 8efb6014
      Ulf Möller 提交于
      Submitted by: Martin Kraemer <martin.kraemer@mch.sni.de>
      8efb6014
  32. 31 1月, 2000 1 次提交
  33. 21 1月, 2000 1 次提交
  34. 18 1月, 2000 1 次提交
  35. 07 1月, 2000 1 次提交
  36. 29 12月, 1999 1 次提交
  37. 03 12月, 1999 1 次提交