Vinícius Ferrão
b53ffaf190
The daemon reads the XML of every request through this parser. A request could declare an entity in its own document type declaration, and the parser expanded it. An entity that refers to other entities grows on each level, so a short request expands into a large document and consumes the memory and the time of the daemon. A client holds a certificate before it can send a request, so this needs an account, but the daemon should not accept the work. Refuse the declaration itself. The option that stops the parser from expanding an entity does not cover an entity that a request names inside an attribute, so it leaves the same growth available through a different part of the document. Measured on XML::Parser 2.46, a request of 204 bytes that names its entity in an attribute still grew to 1014 bytes with that option set, which is what the parser does without it. No request that xCAT sends carries a document type declaration. The client builds every request with XML::Simple, which does not write one. The handler that refuses an external entity stays, so a parser that reaches it by another route still refuses to read the named file.
xCAT
xCAT is a toolkit for deployment and administration of clusters of all sizes.
The xCAT sunset was only a quick eclipse
Dear xCAT Community,
The xCAT sunset has changed course. VersatusHPC has been invited to join the xCAT Consortium, and future development will move toward direct upstream contributions coordinated with the Consortium and its existing member companies.
That matters most for Enterprise Linux 10 (EL10). EL10 support is coming to xCAT, restoring a future operating-system path for sites that still rely on xCAT. This is an important change from the previous sunset guidance, where the lack of an EL10 path was one of the strongest reasons to move away from xCAT.
The xCAT Consortium continues to recommend Confluent as the long-term successor to xCAT, and that remains the Consortium position. Users planning new cluster-management deployments should evaluate Confluent and its xCAT comparison documentation.
At the same time, xCAT is no longer sunsetted. The Consortium and participating companies will continue updating xCAT while there is community and user demand for it.
In summary:
- xCAT development is continuing upstream through the Consortium and participating companies.
- Enterprise Linux 10 support is coming.
- Confluent remains the Consortium-recommended successor and migration path.
- xCAT updates will continue while there is community and user demand.
We want to thank the xCAT Consortium and community for keeping this project moving. The sun went behind the moon for a moment, but xCAT is still here.
For more information on Confluent and how to get started, please visit the Confluent: Project Page, Documentation or Confluent vs xCAT comparison.
With thanks,
The xCAT Consortium
Documentation
xCAT Documentation is hosted on Read The Docs: https://xcat-docs.readthedocs.io
Status
| xCAT Version | Build Status |
|---|---|
| Latest (master branch) | |
| Stable (latest release) |
Looking for older versions?
Open Source License
xCAT is made available under the EPL license: https://opensource.org/licenses/eclipse-1.0.php
Developers
Want to help? Check out the developers guide!