Timeline for Curling a https url via a proxy results in NSS error 5938
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2018 at 22:27 | history | tweeted | twitter.com/StackUnix/status/996154963100426242 | ||
| May 1, 2018 at 23:17 | comment | added | denormalizer | Yeahp jumping through a lot of hoops. Their reasoning is that it's currently working for them (except to our machine). And therefore there could be a big impact if they do upgrade and potentially break it for everyone else. | |
| May 1, 2018 at 17:01 | comment | added | saleetzo | @denormalizer sounds like you are going through a lot of hoops to use an outdated and possible insecure version of curl. This is a very simply update -- just wondering why they are so against updating curl? | |
| May 1, 2018 at 7:47 | comment | added | denormalizer | Hi Vlastimil, most solutions out there regarding the 5938 error suggests upgrading curl and/or nss. At the moment, this isn't an option, at least on our B2B partner's end. | |
| May 1, 2018 at 6:06 | comment | added | Vlastimil Burián | May be related: unix.stackexchange.com/a/310696/126755 | |
| May 1, 2018 at 5:04 | comment | added | denormalizer | Hmm. Still same error: NSS error -5938 | |
| May 1, 2018 at 1:19 | comment | added | denormalizer | I should have tried this first. Let me get them to try. They're a bit slow to get back | |
| May 1, 2018 at 1:06 | history | edited | denormalizer | CC BY-SA 3.0 | Trying to be clearer |
| May 1, 2018 at 1:04 | comment | added | saleetzo | Are they able to get the information if they use curl with -k to complete an insecure connection? Normally you'd want to remedy the version or cert issue, but if they don't want to update curl maybe you can just bypass the SSL check... | |
| May 1, 2018 at 0:59 | history | asked | denormalizer | CC BY-SA 3.0 |