5 ms·

Yesterday I was wondering why the self signed root certificate and the certificates I added to my debian install didn't work with httpie (ssl warning) but did w

Yesterday I was wondering why the self signed root certificate and the certificates I added to my debian install didn't work with httpie (ssl warning) but did work with curl (and the browsers I added the RootCA to). I found the explanation: https://github.com/httpie/httpie/issues/480 https://github.com/httpie/httpie/issues/480 httpie doesn't look into /usr/local/share/ca-certificates but apparently it's not httpie's fault, it's the python requests library that doesn't check that folder. I don't know what to think of it and who is supposed to fix it. But I am back to curl with my tail between the legs (because I oversold httpie to my coworkers) for now. There's only one place where the bucket stops with curl.

EdwardDiego 3y ago
Gosh sigmavirus24 is a salty chap.
- imron 3y ago
  I read the thread after seeing your comment, and it strikes me that besides the first comment being a little brusque, sigmavirus24 comes across as both calm and helpful - doubly so given that the original issue appears to have been PEBKAC related > I think I forgot to run "pip3 uninstall" and ran only "pip uninstall" as I had to use python3 to get working ssl in the first place.
  - DangitBobby 3y ago
    The issue is still open, so it has nothing to do with PEBKAC. "A little brusque" is definitely underselling it. That was a fine display of internet assholery.
  - EdwardDiego 3y ago
    My interpretation of saltiness was also formed by reading the linked requests issue. Just sarcasm went unnecessary.
drunkpotato 3y ago
I ran into this the other day as well. You can override the REQUESTS_CA_BUNDLE env var to point to your own certs. https://stackoverflow.com/a/37447847 https://stackoverflow.com/a/37447847
IshKebab 3y ago
For once I would say it isn't Python's fault either. There are at least 10 different locations that certificates can be stored at on various Unix variants and Linux distros. Go checks them all, which is probably the only sane solution, but seriously come on Unix devs... Is it that hard to pick a standard location?

EdwardDiego 3y ago

Gosh sigmavirus24 is a salty chap.

imron 3y ago
I read the thread after seeing your comment, and it strikes me that besides the first comment being a little brusque, sigmavirus24 comes across as both calm and helpful - doubly so given that the original issue appears to have been PEBKAC related > I think I forgot to run "pip3 uninstall" and ran only "pip uninstall" as I had to use python3 to get working ssl in the first place.
- DangitBobby 3y ago
  The issue is still open, so it has nothing to do with PEBKAC. "A little brusque" is definitely underselling it. That was a fine display of internet assholery.
- EdwardDiego 3y ago
  My interpretation of saltiness was also formed by reading the linked requests issue. Just sarcasm went unnecessary.

drunkpotato 3y ago

I ran into this the other day as well. You can override the REQUESTS_CA_BUNDLE env var to point to your own certs. https://stackoverflow.com/a/37447847 https://stackoverflow.com/a/37447847

IshKebab 3y ago

For once I would say it isn't Python's fault either. There are at least 10 different locations that certificates can be stored at on various Unix variants and Linux distros. Go checks them all, which is probably the only sane solution, but seriously come on Unix devs... Is it that hard to pick a standard location?