1. 21 1月, 2007 1 次提交
  2. 02 12月, 2006 2 次提交
  3. 19 7月, 2006 1 次提交
  4. 10 6月, 2006 1 次提交
  5. 16 2月, 2002 1 次提交
  6. 03 1月, 2002 1 次提交
    • R
      Because Rijndael is more known as AES, use crypto/aes instead of · 6f9079fd
      Richard Levitte 提交于
      crypto/rijndael.  Additionally, I applied the AES integration patch
      from Stephen Sprunk <stephen@sprunk.org> and fiddled it to work
      properly with the normal EVP constructs (and incidently work the same
      way as all other symmetric cipher implementations).
      
      This results in an API that looks a lot like the rest of the OpenSSL
      cipher suite.
      6f9079fd
  7. 04 6月, 1999 1 次提交
  8. 30 1月, 1999 1 次提交
  9. 24 1月, 1999 1 次提交
  10. 17 1月, 1999 1 次提交
    • D
      Time to blow up the source tree :-) This is the beginning of support for · f6aed2cd
      Dr. Stephen Henson 提交于
      GeneralizedTime. At several points PKIX specifies that GeneralizedTime can be
      used but OpenSSL doesn't currently support it. This patch adds several files
      and a bunch of functions.
      
      Of interest is the ASN1_TIME structure and its related functions. At several
      points certificates, CRLs et al specify that a time can be expressed as a
      choice of UTCTime and GeneralizedTime. Currently OpenSSL interprets this
      (wrongly) as UTCTime because GeneralizedTime isn't supported. The ASN1_TIME
      stuff provides this functionality.
      
      Still todo is to trace which cert and CRL points need an ASN1_TIME and modify
      the utilities appropriately and of course fix all the bugs.
      
      Note new OpenSSL copyright in the new file a_time.c. I didn't put it in
      a_gentm.c because it is a minimally modified form a_utctm.c .
      
      Since this adds new files and error codes you will need to do a 'make errors'
      at the top level to add the new codes.
      f6aed2cd