Point security reports at security@ctrliq.com - #22
Open
blaipr wants to merge 1 commit into
Open
Conversation
SECURITY.md was inherited unchanged from awx-operator and directs vulnerability reports to security@ansible.com, which routes disclosures for this operator to a project that does not maintain it. Replace it with the same policy already used in ctrliq/ascender-collection, reporting to security@ctrliq.com.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SUMMARY
SECURITY.mdwas inherited unchanged fromawx-operatorand directs vulnerability reports to security@ansible.com. Anyone following it discloses a flaw in this operator to a project that does not maintain it and cannot ship a fix.This replaces it with the same policy already in use in ctrliq/ascender-collection, reporting to security@ctrliq.com, so the Ascender repos are consistent. The supported-versions table matches the operator's current release line (25.x since 25.5.0).
Kept deliberately separate from #17 so it doesn't conflict with the rebrand branch — this stands on its own regardless of how the branding work lands, and #17 does not touch this file.
ISSUE TYPE
COMPONENT NAME