You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Research and validate methods to enhance ACL's resilience to spoofing
Describe the solution you'd like
NA
Describe alternatives you've considered
None
Additional context
In a Kubernetes environment, Routr faces challenges with ACL due to obfuscated IP addresses. IPs are sourced from SIP headers, which are not immune to spoofing.
The text was updated successfully, but these errors were encountered:
As of today, I'm restarting this research. The current approach I'm investigating combines the From, Request-URI, Via, Contact, and Route headers.
The idea is to create an algorithm that examines various headers based on a selected policy. The policy will indicate which header(s) to consider. For example, the following ACL mandates using the Contact header as the primary source of trust:
Is your feature request related to a problem?
Research and validate methods to enhance ACL's resilience to spoofing
Describe the solution you'd like
NA
Describe alternatives you've considered
None
Additional context
In a Kubernetes environment, Routr faces challenges with ACL due to obfuscated IP addresses. IPs are sourced from SIP headers, which are not immune to spoofing.
The text was updated successfully, but these errors were encountered: