Bug 131112

	Up to MySQL 5.0.x the know WITH_OPENSSL mean "compile with OpenSSL library".
There has been already bundled YASSL, but our port doesn allow to compile against it.

	Starting with MySQL 5.1 server port, the WITH_OPENSSL mean "compile with bundled
YASSL library" and our port doesn't allow compiling against OpenSSL.

	Unfortunatelly, the YASSL and OPENSSL SSLs are not interoperable. At least
in MASTER-SLAVE replication, the client compiled with YASSL can never connect to
server compiled with OpenSSL and vice versa.

	It's known problem, such problem has been with 5.0 as well but nobody found 
the reason for interoperability problem yet. The mixed OpenSSL/YASSL in one MySQL 
domain is not recommended.

The change in the port, "only against OpenSSL" to "only against YASSL" create the
problem with interoperability between 50 and 51 port and broke easy upgrade 
from 5.0 to 5.1

Fix: Allow us to compile 5.1 server using OpenSSL again. In the best case 
- return the original meaning to WITH_OPENSSL knob and create another for YASSL.
How-To-Repeat: 	Compile 5.0 and 5.1 server, both with WITH_OPENSSL. Configure 5.0 to be MASTER
and 5.1 to be slave (it's supported configuration - in the fact - it's mandatory step
in the process of replication cluster 5.0->5.1 upgrade). The slave will be unable
to connect. Recompile one of the server against other SSL library and problem disappear with
no change in configuration.