Chef Ideas

We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.

We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.

Thanks for collaborating with us!

enable 'Secure Transport' for curl/libcurl on macOS to take advantage of system keychain

Having that feature enabled would allow curl to become aware of keychain-deployed certificates/keys. both for trust and for auth on macOS. 

This would make the software aware of internal root certificate trust that are already managed on the system.

  • Guest
  • Jan 31 2020
  • Out of Scope
  • Attach files
  • Admin
    Tim Smith commented
    10 Feb, 2021 03:50am

    In this scenario the user is going to need to point to the full path system curl vs. the embedded curl. We can't enable both our packaged openssl and secure transport at the same time. Due to that there's no way for us to ship this change without breaking other parts of the current kit.

  • Bryan McLellan commented
    24 Jul, 2020 03:59pm

    jok, could you provide a more specific example of a use case that shows why you couldn't use the system curl instead of the curl in our package?

  • Guest commented
    31 Jan, 2020 04:47pm

    In addition, from a user-perspective, this might also allow for use of hardware tokens integrated into the system.