Repository navigation
feat: use soc@appalachiancloud.co as the security.txt contact - #41
Merged
Merged
Conversation
Replaces the personal address with the estate's per-domain soc@ contact. This site is a subdomain and has no MX of its own, so it uses the parent apex's address rather than soc@edulab.appalachiancloud.co, which would not resolve. The address is served by the Google Workspace catch-all rather than a real mailbox — a standing dependency now recorded in AGENTS.md and the CHANGELOG, since switching Workspace to explicit recipients would bounce it silently on the one channel a reporter is told to use. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Y7PCTaciw6HtEC1eLL185
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
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.
Switches the
security.txtcontact from a personal address to the estate's per-domainsoc@convention, at the owner's direction.This site is a subdomain, so it uses the parent apex's address —
soc@appalachiancloud.co, notsoc@edulab.appalachiancloud.co.edulab.appalachiancloud.cocarries no MX of its own, so an address at the subdomain would not resolve.One judgement call worth checking
These addresses resolve through the Google Workspace catch-all on each apex — there is no
soc@mailbox behind them. That is fine today, but it is a standing dependency on exactly the channel a security reporter is told to use: if Workspace is ever switched to explicit recipients, every one of these addresses starts bouncing, and nothing would alarm on it. Recorded inAGENTS.mdand the CHANGELOG rather than left implicit.I could not verify delivery from here — an SMTP
RCPT TOprobe was blocked by tooling — so this rests on the owner's account of the catch-all. Worth a one-off confirmation: mailsoc@on each domain and check it arrives.Renewal unchanged
Expires: 2027-08-31T00:00:00.000Z; matrix and checklist inmountain-infra/AGENTS.mdand its renewal issue.🤖 Generated with Claude Code
https://claude.ai/code/session_012Y7PCTaciw6HtEC1eLL185