yusiboyz/platform
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Transport Security: Finish Cookie Hardening, TLS Verification, and Proxy Controls #7

New Issue
Closed
opened 2026-03-29 08:35:00 -05:00 by yusiboyz · 1 comment
yusiboyz commented 2026-03-29 08:35:00 -05:00
Owner
Copy Link

This issue covers cookie, HTTPS, TLS verification, and proxy hardening.

Problems:

  • Gateway cookie handling was partially hardened but logout cookie clearing is still inconsistent
  • Gateway still disables TLS certificate and hostname verification globally
  • Image proxy now has an allowlist, but transport verification is still weakened

Files:

  • gateway/responses.py
  • gateway/auth.py
  • gateway/config.py
  • gateway/integrations/image_proxy.py

Acceptance criteria:

  • Session set and clear operations use consistent secure cookie attributes
  • TLS certificate and hostname verification are enabled by default
  • Any exceptions for internal services are explicitly scoped, not global
  • Image proxy remains allowlisted and rejects internal/private targets
This issue covers cookie, HTTPS, TLS verification, and proxy hardening. Problems: - Gateway cookie handling was partially hardened but logout cookie clearing is still inconsistent - Gateway still disables TLS certificate and hostname verification globally - Image proxy now has an allowlist, but transport verification is still weakened Files: - gateway/responses.py - gateway/auth.py - gateway/config.py - gateway/integrations/image_proxy.py Acceptance criteria: - Session set and clear operations use consistent secure cookie attributes - TLS certificate and hostname verification are enabled by default - Any exceptions for internal services are explicitly scoped, not global - Image proxy remains allowlisted and rejects internal/private targets
yusiboyz added this to the Immediate milestone 2026-03-29 08:43:51 -05:00
yusiboyz commented 2026-03-29 13:50:24 -05:00
Author
Owner
Copy Link

Completed in 7c05ef1 + 9e13984 — _internal_ssl_ctx removed entirely. proxy.py uses plain urlopen() (all internal services are HTTP). ssl import removed from config.py. External calls (OpenAI, SMTP2GO) use default TLS.

**Completed in 7c05ef1 + 9e13984** — _internal_ssl_ctx removed entirely. proxy.py uses plain urlopen() (all internal services are HTTP). ssl import removed from config.py. External calls (OpenAI, SMTP2GO) use default TLS.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
critical
dependencies
high
immediate
medium
next
ops
performance
security
No Label
Milestone
No items
No Milestone Immediate
Projects
Clear projects
No project
Assignees
Clear assignees
yusiboyz
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yusiboyz/platform#7
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?