fix: networking in corporate root-CA environments on Mac OS - #1546
fix: networking in corporate root-CA environments on Mac OS#1546geoffp wants to merge 2 commits into
Conversation
This is so that network operations work in corporate environments that use their own root CA on (at least) Mac OS.
|
@geoffp is attempting to deploy a commit to the Gal Schlezinger's projects Team on Vercel. A member of the Team first needs to authorize it. |
🦋 Changeset detectedLatest commit: 38dc78d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Thanks for picking this up and taking it further. |
|
Thank you! Added. |
|
@Schniz it would be great to have your eyes on this! |
|
Hey @Schniz any chance this PR can be looked at? I'm part of a big enterprise that's essentially stuck on nvm ( 🤮 ) because of this limitation. Thanks! |
|
Same -- this is all that's standing in the way of large-scale adoption at my company. |
This is so that network operations work in corporate environments that use their own root CA on (at least) Mac OS. It's a really simple fix: have reqwest use the
native-tlsfeature so thatfnmwill use the OS-native TLS stack, which in cases like mine are pre-configured to use the certs that work.This fixes #1432 and possibly (maybe) #520, #1253, #1241, and #1064.
Apologies and thanks to @ripecosta who started this process in #1538!