As Casuarina is still a small project in an experimental state all responses to security issues will by best effort, without guaranteed timelines. Nonetheless we appreciate any issues being reported responsibly.
If you discover a security issue related to Casuarina it can be privately reported to security@casuarina.org. Please keep the report clear, and concise, and include step-by-step instructions to reproduce the issue.
Casuarina is a downstream project of Chimera Linux therefore it’s better for everyone if we can help out there too. Ideally package updates are submitted to Chimera as well. Keep in mind they will need to built, installed, and tested on a Chimera system before you do this. New packages with limited userbases can be submitted to Casuarina directly. If the package is more widely used then it makes sense to submit it to Chimera too.
Casuarina does not aim to erase Chimera. In fact it should remain pretty clear that it is a Chimera descendant. As a result there is no aim to globally replace all references to Chimera. The primary place renames are performed is in identification. Casuarina should uniquely identify itself.
This means values in /etc/os-release are changed, identification of the platform
in packages is changed. What doesn’t change is tools and software, as chimera
is part of the name. E.g. chimerautils remains as-is, as do the chimera-bootstrap
and chimera-chroot scripts used during installation.
In line with Chimera, and given the desire to upstream changes, “AI”-generated contributions are strictly prohibited. This includes, but is not limited to: code, documentation, bug reports, pull-request descriptions, and forum posts.
As per the license, Casuarina Linux:
is provided by the copyright holders and contributors “as is” and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the copyright holder or contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.