ended5월 13일· 1 sources
Why HTTPS_PROXY Cannot Prevent Agent Egress: Three Kernel-Level Gaps
HTTPS_PROXY만으로는 부족하다: 커널이 못 막는 3가지 우회 경로
Why it matters
Setting HTTPS_PROXY provides false security: agents can bypass it through subprocess environment clearing, direct socket APIs, and transports like gRPC and QUIC that ignore the environment variable entirely. The kernel enforces none of these restrictions by default. True egress control requires kernel-level enforcement via nftables or Kubernetes NetworkPolicy.
1
Sources
+0
24h
—
Growth
75d
Active
HTTPS_PROXYkernel enforcementegress filteringsubprocess spawningraw socketsgRPC