Load dependencies by name

[aleksei-fedotov]

Description

This PR allows loading dependencies by module name only as it is proposed in this RFC. In particular, it:

• Verifies signatures of all loaded modules.
• Changes loading of Thread Composability Manager using its module name instead of full path.

The signature verification is enabled by default. To disable it explicitly, user needs specifying -DTBB_VERIFY_DEPENDENCY_SIGNATURE=OFF in the invocation command of CMake. In this case the warning message appears:

CMake Warning at CMakeLists.txt:231 (message):
  Verification of a dependency signature during dynamic run-time linking is
  explicitly disabled.This may lead to security vulnerabilities.  It is
  recommended to leave it enabled by default or set
  TBB_VERIFY_DEPENDENCY_SIGNATURE ON to enable it explicitly.

The patch also adds optional reporting of dynamic link issues. Examples of the output:

oneTBB dynamic link warning: The module "<path-to-dll>" is unsigned or has invalid signature.
oneTBB dynamic link warning: The module "<path-to-dll>" was not found. System error: 126

The issues reporting is disabled by default and can be enabled by setting TBB_DYNAMIC_LINK_WARNING macro during the build.

[egfefey]

Similar here: Is the case for an expired certificate covered somewhere?

[aleksei-fedotov]

It is covered by untrusted root case as the whole chain of certificates is checked.

[egfefey]

Better to use LONG instead of auto to prevent ambiguity and unintended typecasting when doing comparisons later with the return code from WinVerifyTrust

[egfefey]

From the security standpoint, this is good for now.
A few notes:

• This is still up for discussion but anything beside ERROR_SUCCESS from WinVerifyTrust should result in an error instead of a warning sometimes. The user always has to option to turn off signature verification if they want, so once it's on, it's either success or failure.
• Might also need review from the TBB team.
• If there are some testing results that we can share, that will be great.

[egfefey]

Update to use SearchPathA is good from the security point of view.

[aleksei-fedotov]

Update to use SearchPathA is good from the security point of view.

Thanks, @egfefey! Then I proceed with productization of this patch.