Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CDN77 is incompatible with Conjure as a domain fronting cloud provider #286

Open
cohosh opened this issue Jan 28, 2025 · 0 comments
Open

Comments

@cohosh
Copy link
Contributor

cohosh commented Jan 28, 2025

This isn't a bug or a request so much as something interesting I learned today while working on the Conjure integration with Tor.

I was debugging why connections to phantom IP addresses that were obtained from our domain fronted registrations were failing, while connections to phantom IPs from non domain-fronted registrations were working just fine. I noticed this in the CDN77 documentation:

X-Forwarded-For + X-Real-IP: This is the IP Address from the TCP connection from which our CDN Edge server received the request. To protect users’ personal data, we anonymize the last octet in the IP and replace it with a trailing zero. For example, if the IP address received from the TCP connection was 192.1.1.1, the anonymized IP will be 192.1.1.0.

This means Conjure's registration api will receive connections seemingly from these "anonymized" IP addresses, forward this to the detector, and the detector will see incoming TCP connections from the client's real IP address, and won't recognize them as phantom sessions.

I don't think there is much to do here, but I wanted to document it somewhere in case someone else came across the same issue.

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

No branches or pull requests

1 participant