I *think* I got them all covered by now, bu please, if you find any more,
tell me and I'll correct it.
PR: 343

always give the expected result on some platforms.

I've covered all the memset()s I felt safe modifying, but may have missed some.

and linker optimizations.
PR: 343

'OpenSSL_0_9_6-stable'.

and linker optimizations.
PR: 343

incorrect.  Fortunately, there is a second check that's correct, when adding
the pads.
PR: 355

incorrect.  Fortunately, there is a second check that's correct, when adding
the pads.
PR: 355

to force the use of Heimdal, and warn if that's used.
PR: 346

PR: 349

to force the use of Heimdal, and warn if that's used.
PR: 346

Submitted by: Sheueling Chang

Submitted by: Nils Larsch

for Montgomery representations.

Submitted by: Sheueling Chang, Bodo Moeller

caching (#288): now internal caching failed (#351):
Make sure, that cipher_id is set before comparing.
Submitted by:
Reviewed by:
PR: 288 (and 351)

caching (#288): now internal caching failed (#351):
Make sure, that cipher_id is set before comparing.
Submitted by:
Reviewed by:
PR: 288 (and 351)

(we can't release it before the CRYPTO_mem_leaks() call!)

Submitted by: Nils Larsch

(we can't release it before the CRYPTO_mem_leaks() call!)

Submitted by: Nils Larsch

defined as follows (according to X.509_4thEditionDraftV6.pdf):

CertificatePair ::= SEQUENCE {
	forward		[0]	Certificate OPTIONAL,
	reverse		[1]	Certificate OPTIONAL,
	-- at least one of the pair shall be present -- }

The only thing I'm not sure about is if it's implicit or explicit tags
that I should count on.  For now, I'm thinking explicit, but will
gladly stand corrected.

Also implement the PEM functions to read and write certificate pairs,
and defined the PEM tag as "CERTIFICATE PAIR".

This needed to be defined, mostly for the sake of the LDAP attribute
crossCertificatePair, but may prove useful elsewhere as well.

Submitted by: Nils Larsch