Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Getting pubkey fingerprint in libcurl
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Ray Satiro via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 15 Mar 2021 00:36:28 -0400
On 3/12/2021 7:13 AM, Morten Minde Neergaard wrote:
> At 01:02, Tue 2021-03-02, Ray Satiro via curl-library wrote:
>> On 2/26/2021 4:10 PM, Morten Minde Neergaard via curl-library wrote:
> [...]
>>> It would be a lot more elegant if there were an option to get the pubkey
>>> fingerprint directly, using the same pattern as CURLOPT_CERTINFO /
>>> CURLINFO_CERTINFO. Suggesting this addition to the curl APIs:
>>>
>>> CURLOPT(CURLOPT_PUBKEY_FINGERPRINT, CURLOPTTYPE_LONG, 309),
> [...]
>> Is this not provided by certinfo already? If not I think it would be easier
>> to add it there in a separate line, pubkey:asdf
> It isn't provided, no.
>
> It might be easier, but I guess my opinion about adding it to
> CURLOPT_CERTINFO is colored by my dislike of populating such a large
> amount of data and sifting through it running a bunch of string
> compares.
>
> The current implementation populates ~20k over 72 different strings for
> some random, somewhat representative pages. That feels like a lot more
> than what I need. But if we want to keep the implementation simple,
> sure, I can try to add it to CURLINFO_CERTINFO =)
It would be good to know if anyone else has an opinion about this.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-03-15
Date: Mon, 15 Mar 2021 00:36:28 -0400
On 3/12/2021 7:13 AM, Morten Minde Neergaard wrote:
> At 01:02, Tue 2021-03-02, Ray Satiro via curl-library wrote:
>> On 2/26/2021 4:10 PM, Morten Minde Neergaard via curl-library wrote:
> [...]
>>> It would be a lot more elegant if there were an option to get the pubkey
>>> fingerprint directly, using the same pattern as CURLOPT_CERTINFO /
>>> CURLINFO_CERTINFO. Suggesting this addition to the curl APIs:
>>>
>>> CURLOPT(CURLOPT_PUBKEY_FINGERPRINT, CURLOPTTYPE_LONG, 309),
> [...]
>> Is this not provided by certinfo already? If not I think it would be easier
>> to add it there in a separate line, pubkey:asdf
> It isn't provided, no.
>
> It might be easier, but I guess my opinion about adding it to
> CURLOPT_CERTINFO is colored by my dislike of populating such a large
> amount of data and sifting through it running a bunch of string
> compares.
>
> The current implementation populates ~20k over 72 different strings for
> some random, somewhat representative pages. That feels like a lot more
> than what I need. But if we want to keep the implementation simple,
> sure, I can try to add it to CURLINFO_CERTINFO =)
It would be good to know if anyone else has an opinion about this.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-03-15