selection macros.

Only use the new informational verify codes if we
specifically ask for them.

Fix typo in docs.

work better in Win32.  Verified by zhu qun-ying <qyzhu@krdl.org.sg>.

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.

BN_mod_mul_montgomery, which calls bn_sqr_recursive
without much preparation.

bn_sqr_recursive requires the length of its argument to be
a power of 2, which is not always the case here.
There's no reason for not using BN_sqr -- if a simpler
approach to squaring made sense, then why not change
BN_sqr?  (Using BN_sqr should also speed up DH where g is chosen
such that it becomes small [e.g., 2] when converted
to Montgomery representation.)

Case closed :-)

make disabled code slightly more correct (this does not solve
the problem though).

in 0.9.6-beta1 and 0.9.6-beta2 and caused the BN_mont_exp_mont_word()
failure (bug report "openssh 2.2.0p1 fails with openssl 0.9.6-beta1").

so disable that part.
Reported by Jeffrey Altman <jaltman@columbia.edu>

disagree on the proper syntax and type names.

Jeffrey Altman reminds us to initialize some variables and ercommends the use of LOadLibrary instead of GetModuleHandle

accordingly.

Submitted by Kevin Steves <ks@hp.se> 3 months ago...

problems with GetCursorInfo, but also adds network statistics and
performance statistics where available.

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

can't be used as a function pointer according the the standards.  Use
a 0 instead and there will be no trouble.

incompatibility between function and data pointers.

(it's similar to the shutdown(..., SHUT_WR) system call
for sockets).

Update docs.

doesn't quite work on WinNT 4 earlier than SP6.  It works fine on
Windows 98 and Windows 2000.

I'm disabling it for now.  What's really needed is some kind of check
to see if GetCursorInfo is safe to call, or alternatively, GetCursor
or GetCursorPos could be used, according to Jeffrey.

sign.

no way to make sure GetCursorInfo will give us a valid answer.

The copy at www.usenix.org is the old version.

- Make sure PCURSORINFO is defined even on systems that do not provide it.
- Change the reference to Peter Gutmann's paper.
- Make sure we don't walk the whole heap lists for performance reasons.
  Jeffrey Altman suggests following Peter Gutmann's advice to keep it
  to 50 heap entries per heap list.