[#11545] - Update cacert.pem to latest Mozilla version
- Closed
- 7 Sep 2016
- Medium
- Build: staging
- # 11545
- Diff
- nicksavov:patch-4
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #: N/A
Summary of Changes
Update cacert.pem to latest Mozilla version
Testing Instructions
None. It's just syncing the file with the official one at http://curl.haxx.se/ca/cacert.pem
Examples of three previous PRs for it that were merged without testing:
#6878
#4296
#3634
Documentation Changes Required
None.
Additional info
Need a clarification if I should be using the Centos cacert.pem or Mozilla's. See conversation at #9367 (comment)
joomla-cms-bot
- | Category | ⇒ | Libraries |
| Status | New | ⇒ | Pending |
| Labels |
Added:
?
|
||
I think we stick with the centos pack. Sadly mozilla time and time again has removed certificates when big entities are still using them (e.g. captcha and AWS previously). Using the centos pack seems to have resolved these problems fairly conclusively.
please check your email
@ggppdk I check my mail all day - dont have anything about cacert in my mail
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11545.
please forget of the mail about cacert, i was wrong about it, lack of sleep ...
I am closing this. Thanks for creating this PR but as stated the mozilla cacert has caused considerable issues and we are sticking with the more complete one from centos
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11545.
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-09-07 07:48:25 |
| Closed_By | ⇒ | brianteeman |
From my perspective this should NOT be using the Mozilla cert