7482b6ebf0
When updating CAs via the CLI, we need to create new copies of all the impacted ckch instances (as in referenced in the ckch_inst_link list of the updated CA) in order to use them instead of the old ones once the updated is completed. This relies on the ckch_inst_rebuild function that would set the ckch_store field of the ckch_inst. But we forgot to also add the newly created instances in the ckch_inst list of the corresponding ckch_store. When updating a certificate afterwards, we iterate over all the instances linked in the ckch_inst list of the ckch_store (which is missing some instances because of the previous command) and rebuild the instances before replacing the ckch_store. The previous ckch_store, still referenced by the dangling ckch instance then gets deleted which means that the instance keeps a reference to a free'd object. Then if we were to once again update the CA file, we would iterate over the ckch instances referenced in the cafile_entry's ckch_inst_link list, which includes the first mentioned ckch instance with the dead ckch_store reference. This ends up crashing during the ckch_inst_rebuild operation. This bug was raised in GitHub #3165. This patch should be backported to all stable branches. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .cirrus.yml | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
Please refer to the following files depending on what you're looking for:
- INSTALL for instructions on how to build and install HAProxy
- BRANCHES to understand the project's life cycle and what version to use
- LICENSE for the project's license
- CONTRIBUTING for the process to follow to submit contributions
The more detailed documentation is located into the doc/ directory:
- doc/intro.txt for a quick introduction on HAProxy
- doc/configuration.txt for the configuration's reference manual
- doc/lua.txt for the Lua's reference manual
- doc/SPOE.txt for how to use the SPOE engine
- doc/network-namespaces.txt for how to use network namespaces under Linux
- doc/management.txt for the management guide
- doc/regression-testing.txt for how to use the regression testing suite
- doc/peers.txt for the peers protocol reference
- doc/coding-style.txt for how to adopt HAProxy's coding style
- doc/internals for developer-specific documentation (not all up to date)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.