Circumstances changed, we are not interested in this feature anymore at
this moment.
Just for the record workarounds using external call to 'openssl' can be
found here:
* https://gitlab.kitware.com/cmake/cmake/merge_requests/105
* https://gitlab.kitware.com/cmake/cmake/merge_requests/108
Rusl
On 13-Sep-16 15:58, Brad King wrote:
On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote:
Will it be okay if CMake will optionally depend on OpenSSL?
Or other third party crypto library?
Currently the only place that needs it is through `curl`, and
that uses either OpenSSL or the
On 09/13/2016 07:42 AM, Ruslan Baratov via cmake-developers wrote:
> Will it be okay if CMake will optionally depend on OpenSSL?
> Or other third party crypto library?
Currently the only place that needs it is through `curl`, and
that uses either OpenSSL or the Windows-native or macOS-native
APIs
Hi,
Currently I'm investigating possibilities of downloading files from
private S3 bucket using CMake. The only real issue I see for now is the
computing of HMAC + SHA1. This look like a work for some new
cryptographic module in family of 'string' functions similar to
'string(MD5|SHA1|...)'.
