Hi,
I'm making an app that's using public key pinning, and it would be very
helpful to have programmatic access to the pubkey fingerprint. The app
currently has a huge and horrible mountain of platform- and
backend-specific code that extracts the public key fingerprint from the
TLS backend before
Hi,
I'm using libcurl in a project I'm doing, and I'd like to specify some
extra flags to the SCHANNEL_CRED struct to enhance security and remove
potential error sources:
SCH_USE_STRONG_CRYPTO:
Disables some older cipher suites.
SCH_CRED_NO_DEFAULT_CREDS
Found a TODO about this flag at
Okay, first thanks for your interest and time to reply to my
suggestion =)
I think the arguments listed in this e-mail are probably enough
to dismiss the idea.
Have a nice weekend!
Cheers,
Emil
On Fri, Feb 26, 2021 at 10:10:01AM +0100, Michael Felt via curl-library wrote:
> a) Long before
a) Long before sendfile() there was/is send_file() in the UNIX world.
b) just read in the linux man pages that sendfile() is limited to 2GB
file transfers
c) imho - too much complexity for read/write activity when one medium
(network) is likely much slower (or faster) than another medium - or
