openssl/apps/nseq.c, branch OpenSSL_0_9_7m

EXIT() may mean return(). That's confusing, so let's have it really mean

2002-12-03T16:34:28Z

exit() in whatever way works for the intended platform, and define OPENSSL_EXIT() to have the old meaning (the name is of course because it's only used in the openssl program)

Reorder inclusion of header files:

2002-07-10T06:57:54Z

des_old.h redefines crypt: #define crypt(b,s)\ DES_crypt((b),(s)) This scheme leads to failure, if header files with the OS's true definition of crypt() are processed _after_ des_old.h was processed. This is e.g. the case on HP-UX with unistd.h. As evp.h now again includes des.h (which includes des_old.h), this problem only came up after this modification. Solution: move header files (indirectly) including e_os.h before the header files (indirectly) including evp.h. Submitted by: Reviewed by: PR:

Use new-style system-id macros everywhere possible. I hope I haven't

2001-02-20T08:13:47Z

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.

On VMS, stdout may very well lead to a file that is written to in a

2000-09-20T13:55:50Z

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.

Use sk__new_null() instead of sk__new(NULL), since that takes care

2000-09-17T18:21:27Z

of complaints from the compiler about data pointers and function pointers not being compatible with each other.

Make gcc 2.95.2 happy again, even under ``-Wall -Wshadow -Wpointer-arith -Wcast-align

2000-02-11T09:47:18Z

-Wmissing-prototypes -Wmissing-declarations -Wnested-externs -Winline''.

Merge some common functionality in the apps, delete

1999-11-12T01:42:25Z

the encryption option in the pkcs7 utility (they never did anything) and add a couple more options to pkcs7.

Additional user data argument to pem_password_cb function type

1999-07-21T20:57:16Z

and to lots of PEM_... functions. Submitted by: Damien Miller

Don't mix real tabs with tabs expanded as 8 spaces -- that's

1999-06-07T20:26:51Z

a pain to read when using 4-space tabs.

Another safe stack.

1999-05-30T15:40:21Z