therefore be static.  Furthermore, send_mem_chars() is unused, so I
#if 0'd it.

Adding a slash between the directoryt and the file is a problem with
VMS.  The C RTL can handle it well if the "directory" is a logical
name with no colon, therefore ending being 'logname/file'.  However,
if the given logical names actually has a colon, or if you use a full
VMS-syntax directory, you end up with 'logname:/file' or
'dev:[dir1.dir2]/file', and that isn't handled in any good way.

So, on VMS, we need to check if the directory string ends with a
separator (one of ':', ']' or '>' (< and > can be used instead [ and
])), and handle that by not inserting anything between the directory
spec and the file name.  In all other cases, it's assumed the
directory spec is a logical name, so we need to place a colon between
it and the file.

Notified by Kevin Greaney <kevin.greaney@hp.com>.

but never made to 0_9_6...
PR: 811

if the give size is 0.

This is a thought that came up in PR 751.

PR: 755
Notified by: Jakub Bogusz <qboosh@pld-linux.org>

Therefore, change all instances of the symbol 'list' to something else.

PR: 758
Submitted by: Frédéric Giudicelli <groups@newpki.org>

compared it to the amount of bits required...
PR: 770
Submitted by: c zhang <czhang2005@hotmail.com>

PR: 771
Submitted by: c zhang <czhang2005@hotmail.com>

PR: 777
Submitted by: Michael Shields <mshields@sunblocksystems.com>

PR: #759
Submitted by: Martin Kraemer <Martin.Kraemer@Fujitsu-Siemens.com>

certain ASN.1 tags (CAN-2003-0851)

prototypes, so I'm removing -Wstrict-prototypes and
-Wmissing-prototypes from my debugging target in favor of
-Wmissing-declarations.  That will make other issues more visible than
in the middle of a thousand warnings telling me there isn't a proper
prototype for this or that function pointer...

that do not have it.

systems and above.
PR: 664

PR: 679

PR: 680

PR: 685

PR: 698

calling X509_verify_cert() in x509.c the cert should
not be added to the trusted store.

one, as required by SSL/TLS specs.

weren't due to that, but to a change on the SCO machines I used for
testing, where my $PATH was suddenly incorrect.

gcc is used to build with) don't take it too well if LD_LIBRARY_PATH
is messed with when linknig programs.  I'm going to assume that it's
OK to leave it unchanged when linking non-shared.

1. CreateToolhelp32Snapshot returns INVALID_HANDLE_VALUE, not NULL, on error.
2. On Windows CE, a snapshot handle is closed with CloseToolhelp32Snapshot,
   not CloseHandle.

fix typo