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 Windows-native or macOS-native
APIs for TLS.
So your suggestion is to extend 'file' command? Like
`file(DOWNLOAD|UPLOAD <url> <out> S3_KEY <key> S3_SECRET <secret>)`?
It looks like curl does support HMAC.
I don't know, will take a look. We need this functionality:
echo -n "${stringToSign}" | openssl sha1 -hmac "${secret}" -binary |
base64
Ruslo
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers
