Skip to content

Harden daemon notification HTTP posts#18

Merged
Svaag merged 1 commit into
mainfrom
fix/notification-http-post
Jun 21, 2026
Merged

Harden daemon notification HTTP posts#18
Svaag merged 1 commit into
mainfrom
fix/notification-http-post

Conversation

@Svaag

@Svaag Svaag commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • send an explicit Engineering Loop User-Agent on daemon notification POSTs so Discord webhooks do not reject Python urllib's default User-Agent
  • relax only OpenSSL's strict legacy-X.509 extension checks for Icinga passive-check POSTs, while keeping CA and hostname verification enabled
  • cover both notification behaviors in daemon tests

Validation

  • uvx ruff check src tests
  • uv run --group dev mypy --strict src
  • uv run --group dev pytest tests/test_phase24_daemon.py

Live context

The loop VM can reach Discord with curl and with urllib once a User-Agent is set. It can validate the Icinga API certificate chain/hostname after installing the Icinga CA, but Python/OpenSSL rejects the legacy internal CA under strict X.509 extension checks unless VERIFY_X509_STRICT is cleared.

@Svaag Svaag merged commit c6ffa04 into main Jun 21, 2026
4 checks passed
@Svaag Svaag deleted the fix/notification-http-post branch June 21, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant