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

The router accepts packets with segments created in the future #4534

Open
jiceatscion opened this issue May 27, 2024 · 0 comments
Open

The router accepts packets with segments created in the future #4534

jiceatscion opened this issue May 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jiceatscion
Copy link
Contributor

jiceatscion commented May 27, 2024

The data plane ietf draft specifies a maximum time to live of a hop in order to limit the potential time window available for brute-force attack on HOP validation MACs. Without dropping segments crafted in the future, that time window could be extended indefinitely by an attacker (by forging a segment with a creation date in an arbitrarily far future - not beyond 2106 though) thereby defeating the purpose of the limited time to live.

In response to the request for clarification in scionassociation/scion-cp_I-D#18 the draft will also state that segments from the future (with some specific tolerance) are to lead to dropping the packet. The code must be made compliant. There also is code in the router that assumes paths are checked for a timestamp in the future with no tolerance. That code backdates the path that it crafts by 10s to compensate for clock drift. This compensation should be part of the check instead (once it exists).

@jiceatscion jiceatscion added the bug Something isn't working label May 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant