1. 26 1月, 2002 2 次提交
  2. 12 9月, 2001 1 次提交
  3. 18 6月, 2001 1 次提交
  4. 30 5月, 2001 1 次提交
    • R
      Extend all the loading functions to take an engine pointer, a pass · 30b4c272
      Richard Levitte 提交于
      string (some engines may have certificates protected by a PIN!) and
      a description to put into error messages.
      
      Also, have our own password callback that we can send both a password
      and some prompt info to.  The default password callback in EVP assumes
      that the passed parameter is a password, which isn't always the right
      thing, and the ENGINE code (at least the nCipher one) makes other
      assumptions...
      
      Also, in spite of having the functions to load keys, some utilities
      did the loading all by themselves...  That's changed too.
      30b4c272
  5. 20 2月, 2001 2 次提交
    • R
      Use new-style system-id macros everywhere possible. I hope I haven't · bc36ee62
      Richard Levitte 提交于
      missed any.
      
      This compiles and runs on Linux, and external applications have no
      problems with it.  The definite test will be to build this on VMS.
      bc36ee62
    • R
      Make all configuration macros available for application by making · cf1b7d96
      Richard Levitte 提交于
      sure they are available in opensslconf.h, by giving them names starting
      with "OPENSSL_" to avoid conflicts with other packages and by making
      sure e_os2.h will cover all platform-specific cases together with
      opensslconf.h.
      
      I've checked fairly well that nothing breaks with this (apart from
      external software that will adapt if they have used something like
      NO_KRB5), but I can't guarantee it completely, so a review of this
      change would be a good thing.
      cf1b7d96
  6. 29 10月, 2000 1 次提交
  7. 26 10月, 2000 1 次提交
  8. 20 9月, 2000 1 次提交
    • R
      On VMS, stdout may very well lead to a file that is written to in a · 645749ef
      Richard Levitte 提交于
      record-oriented fashion.  That means that every write() will write a
      separate record, which will be read separately by the programs trying
      to read from it.  This can be very confusing.
      
      The solution is to put a BIO filter in the way that will buffer text
      until a linefeed is reached, and then write everything a line at a
      time, so every record written will be an actual line, not chunks of
      lines and not (usually doesn't happen, but I've seen it once) several
      lines in one record.  Voila, BIO_f_linebuffer() is born.
      
      Since we're so close to release time, I'm making this VMS-only for
      now, just to make sure no code is needlessly broken by this.  After
      the release, this BIO method will be enabled on all other platforms as
      well.
      645749ef
  9. 10 9月, 2000 1 次提交
  10. 06 9月, 2000 3 次提交
  11. 04 9月, 2000 1 次提交