Signed-off-by: Nchunseoklee <chunseok.lee@samsung.com>


Commit migrated from https://github.com/dotnet/corefx/commit/2a6244795ba341b449deb05f9ed452a9663c936b

Removing comment for certificate matching f*.com and foo.com. The decision was not to support such matching.


Commit migrated from https://github.com/dotnet/corefx/commit/69952cc756503a32d085a7fb175a073e9994e0ce

Commit migrated from https://github.com/dotnet/corefx/commit/f21e02e94acc52694a76b8cce42feefe186cdb2d

Commit migrated from https://github.com/dotnet/corefx/commit/0bb5ad77c6ad275e0087f844982828132f830685

Commit migrated from https://github.com/dotnet/corefx/commit/adc3578b0129e0f78838d455a28ee0b56e71238a

Commit migrated from https://github.com/dotnet/corefx/commit/731b9f64f0461a141024292c2c11bd3ad944a2ce

Commit migrated from https://github.com/dotnet/corefx/commit/ee50d81c2008fed04198f7c9ca8980bfd6431f63

Commit migrated from https://github.com/dotnet/corefx/commit/0e53c1bbf23d8036ab108883b5516c8fbaa44a57

Commit migrated from https://github.com/dotnet/corefx/commit/b84524cf58cb8bebb3d1931b6326b9cbeb07e60a

* Enable distro agnostic build of System.Security.Cryptography.Native

If the FEATURE_DISTRO_AGNOSTIC_SSL is enabled, the System.Security.Cryptography.Native
doesn't link to libssl / libcrypto at build time. It uses a shim that opens the
libssl shared library with versioned so name specific for the platform and gets all needed
API function pointers using dlsym and stores them in global variables.
The calls to those APIs are then redirected through these pointers.

I have verified that our code doesn't access any data members in structures with layout
that can vary based on compilation options of the OpenSSL and that can have variable
offset. The only direct access of this kind that we were using, the X509::sha1_hash,
was replaced by call to recompute the hash, based on @bartonjs suggestion.

There are couple of functions that we use and that don't have to exist in the libssl when
it is compiled with particular options. These were handled at the build time before, now
I have also added runtime handling of this case.

Finally, I have added verification of the System.Security.Cryptography.Native.OpenSsl.so
to make sure it doesn't have any undefined symbols. This could happen if someone adds
usage of a new OpenSSL API and doesn't add its name to the opensslshim.h. The build fails
in this case and lists all the undefined symbols.


Commit migrated from https://github.com/dotnet/corefx/commit/4492e48ea36ee127735bc41e58c2994e81f6b5ac

Commit migrated from https://github.com/dotnet/corefx/commit/732d65134d71b95763da643fd93fbeeef6ebcb97

Commit migrated from https://github.com/dotnet/corefx/commit/5132acbc342df7f04f1852c0f636f810700528d7

Commit migrated from https://github.com/dotnet/corefx/commit/b42dc32d666d9c36f228b58b652b1512403c31de

Let's the language handle overflow detection.


Commit migrated from https://github.com/dotnet/corefx/commit/3973abe061bcf69031aeeff0fe5df2928d90e812

Use the builtins when available, otherwise fall back to using ClrSafeInt.


Commit migrated from https://github.com/dotnet/corefx/commit/0d41ce60751a86a100250f2ac93b7d8693ac6a61

Made a minimal set of changes to get safemath/debugmacrosext to compile on Linux and macOS with the compiler versions being used in the repo, the default warnings enabled, and the lack of other files that coreclr depends on.


Commit migrated from https://github.com/dotnet/corefx/commit/64a7c3bd04ac23de5e336fd4d0b9be73064ee759

We'd like to be able to use builtins for overflow checking, but the relevant builtins (e.g. __builtin_mul_overflow) aren't available with the compiler versions we currently use on all platforms.  In the meantime, we'll use the ClrSafeInt implementation from coreclr.

This commit brings over the files, but they don't yet compile.


Commit migrated from https://github.com/dotnet/corefx/commit/df73b81a5386249d001d9db9a4605f4f97e5e3c5

Commit migrated from https://github.com/dotnet/corefx/commit/d3e301d1d50912feddcbe371ae328babf9090760

Commit migrated from https://github.com/dotnet/corefx/commit/60e8234ea282d92654f7dc964f80fa709d28575b

To avoid exceptions propagating out of native shims and crashing at interop boundary.


Commit migrated from https://github.com/dotnet/corefx/commit/02dda0a64c651573928fbafe0218f023890442d4

Commit migrated from https://github.com/dotnet/corefx/commit/7b97edd23eeb1ce76f3d19100b4cfc67611a767e

Commit migrated from https://github.com/dotnet/corefx/commit/9a44a22fac49bf00d21ba42a7f64e849edcc5590

Commit migrated from https://github.com/dotnet/corefx/commit/8e0f583c1fd037e0e1cec5e93f841e3d37a475e9

These were triggering the memmove assert in memcpy_s, as the src and the dst are the same exact location.


Commit migrated from https://github.com/dotnet/corefx/commit/bd3d3d73923f8345d0d4e1cb5903e4360025d88e

Add a memcpy_s helper and use it everywhere memcpy is currently used.  The only remaining memcpy usage is the one in memcpy_s itself.


Commit migrated from https://github.com/dotnet/corefx/commit/539e4c7830712467e6d33ec62ecb21b8bb3050a5

Every other file in the library is compiled as C++.  Change this one to be as well, both for consistency and so that we can use the same memcpy_s helper to be used elsewhere.


Commit migrated from https://github.com/dotnet/corefx/commit/1633043ac9f218f5d59f5a2e67c1bec953309177

* Add missing System.IO.Pipes API members

- Adds/Exposes:
    - NamedPipeServerStream.MaxAllowedServerInstances
    - NamedPipeServerStream.RunAsClient(System.IO.Pipes.PipeStreamImpersonationWorker)
    - PipeStream.IsHandleExposed
    - PipeStream.CheckPipePropertyOperations
    - PipeStream.CheckReadOperations
    - PipeStream.CheckWriteOperations
    - PipeStream.InitializeHandle(Microsoft.Win32.SafeHandles.SafePipeHandle,System.Boolean,System.Boolean)
    - PipeStreamImpersonationWorker
- Of the above, only RunAsClient required a new implementation (for Unix)
- Adds basic tests for all of the above.
- Some changes to the interop code were required for both Windows and Unix. Those will likely need to be merged in a different PR before this one to enable testing.
- Required updating the default version of the project to netstandard17 from netstandard13.

* Clean up pipes RunAsClient build

* Disable RunAsClient test until packages update with new native code

* Add win32 primitives to pipes project.json


Commit migrated from https://github.com/dotnet/corefx/commit/a4f243fedb1298294587495d5fdea85dd3a7ab08

Enabled for .Csp via CAPI, and .Algorithms for Windows (via Cng), Linux (via OpenSsl) and Apple.


Commit migrated from https://github.com/dotnet/corefx/commit/d2ff60b619a0bfaca341501432f75e50ec77a6da

The native System.Native.so build fails on Alpine Linux with a signed to unsigned
comparison warning in the expansion of the CMSG_NXTHDR macro. The issue is in the
macro definition in the platform headers, so I am adding suppression of that warning
for the macro expansion.


Commit migrated from https://github.com/dotnet/corefx/commit/a87cc03af0493d445b60f6700ab7ca2c7ab9b3fb

Commit migrated from https://github.com/dotnet/corefx/commit/70e823293943b13966448d863625a847a15ebf9c

The ExclusiveAddressUse socket option is a Windows-specific option that, when set to "true," tells Windows not to allow another socket to use the same local address as this socket.  This is only needed on Windows because it otherwise (at least in some versions/configurations) allows any socket with the ReuseAddress option set to "steal" the address from a socket that did not have *any* options set.

On Unix, we previously treated this as an "unsupported" option.  However, it is recommended to set this option to "true" on Windows, to avoid malicious theft of a service's address, so we need to support the option, in some fashion, on Unix, so that it's possible to write portable code that works reliably everywhere.  Since the *only* behavior on Linux/OSX is equivalent to "ExclusiveAddressUse=true" on Windows, we implement this option as a no-op if it's set to "true," and as an unsupported option if set to "false."  (It's possible that we could come up with a better failure for the "false" case, but I'm treating it as "unsupported" for compatiblity with the 1.0 release).

Another related option is ReuseAddress.  On Windows, this option allows a socket's address *and* port to be reused.  It's equivalent to *two* native options on Unix: SO_REUSEADDR and SO_REUSEPORT.  Again, for portability, we need an option that will work roughly the same way on all platforms.  We could introduce a new option (ReuseAddressAndPort?) but existing code is already using the current ReuseAddress option.  So this change makes ReuseAddress set both SO_REUSEADDR and SO_REUSEPORT on Unix.  If we need to support these options individually, on Unix only, in the future, we'll need to introduce two new options (maybe ReuseAddressOnly and ReusePort) which will likely need to be treated as "unsupported" options on Windows.  For now, no need for managed support for more fine-grained options has been demonstrated.

For more information on the underlying native options on Windows, Linux, OSX, etc., see this great writeup [on stackoverflow](http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and-so-reuseport-how-do-they-differ-do-they-mean-t).  Also, the Windows docs [discuss the SO_EXCLUSIVEADDR option](https://msdn.microsoft.com/en-us/library/windows/desktop/cc150667(v=vs.85).aspx) in depth.


Commit migrated from https://github.com/dotnet/corefx/commit/875675ff1296a45f6007cac5f88bbaebe0ebff2b

If OpenSSL is installed in a manner that allows it to be discovered by find_package,
but the headers are not in the default include path, the build fails.

The fix only requires that we append the include directive that find_package set for us,
as a SYSTEM dependency so that we don't get warnings about OpenSSL's headers under our
compiler.

The minimal installation version on OSX:
* brew install openssl
* mkdir -p /usr/local/lib/pkgconfig
* ln -s /usr/local/opt/cellar/openssl/lib/libcrypto.1.0.0.dylib /usr/local/lib/
* ln -s /usr/local/opt/cellar/openssl/lib/libssl.1.0.0.dylib /usr/local/lib/
* ln -s /usr/local/opt/cellar/openssl/lib/pkgconfig/libcrypto.pc /usr/local/lib/pkgconfig/
* ln -s /usr/local/opt/cellar/openssl/lib/pkgconfig/libssl.pc /usr/local/lib/pkgconfig/
* ln -s /usr/local/opt/cellar/openssl/lib/pkgconfig/openssl.pc /usr/local/lib/pkgconfig/

The first two commands allow the versioned ABI to be discovered at runtime, and the
latter three register the information needed for find_package.


Commit migrated from https://github.com/dotnet/corefx/commit/46ca49eaea0ad275243cf31bbf1c2853f1a1da7f

Commit migrated from https://github.com/dotnet/corefx/commit/332e6ba4b239c2324c69d72b020c8342f3a34a37

Commit migrated from https://github.com/dotnet/corefx/commit/ae975bd232e04602b148554745ef0cc04b66af86

Commit migrated from https://github.com/dotnet/corefx/commit/1db4eff07ed9530b4b73e99d8ca009686e38e2c2

Commit migrated from https://github.com/dotnet/corefx/commit/5d6658bc8ce0238ae089eaaca9f2138696e65881

Interface names returned from getifaddrs may refer to an aliased network
device, i.e. "wlan:0". Previously, we were returning this value from the
shim function, and managed code was then treating "wlan" and "wlan:0" to
be distinct network interfaces. Instead, we normalize the interface names
returned from the shim by calling if_indextoname to obtain the "true"
interface name.


Commit migrated from https://github.com/dotnet/corefx/commit/e2f5a3ccb55dfc8c8b811ab44ebbd0f3fa841785

Add support for DSA to System.Security.Cryptography.Algorithms.dll

Commit migrated from https://github.com/dotnet/corefx/commit/40095408a1f2cfeb5ebbf388a41ec29f54af838e

Commit migrated from https://github.com/dotnet/corefx/commit/37d5d9d299c230575f4033afb006f2e2da87a457

Commit migrated from https://github.com/dotnet/corefx/commit/bdc37d4898d96dd67568fc2267426ca8429504f5