We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 protocol says:
drop the oldest responder that did not send a message to it
The code do decide if "that did not send a message to it" applies is:
saltyrtc-client-java/src/main/java/org/saltyrtc/client/signaling/InitiatorSignaling.java
Line 430 in d01e553
Pub if we have a known trusted receivers public key then here:
Line 403 in d01e553
We set the state to TOKEN_RECEIVED for every new responder before they send us any message.
Hence as long as I didn't overlook anything we won't ever drop any old responders as we assume we got valid token message from all of them.
The text was updated successfully, but these errors were encountered:
Agree that there is an issue introduced by the state skipping even though the responder is still inactive.
Security impact: Minor, DoS with prior knowledge required.
Sorry, something went wrong.
No branches or pull requests
The protocol says:
The code do decide if "that did not send a message to it" applies is:
saltyrtc-client-java/src/main/java/org/saltyrtc/client/signaling/InitiatorSignaling.java
Line 430 in d01e553
Pub if we have a known trusted receivers public key then here:
saltyrtc-client-java/src/main/java/org/saltyrtc/client/signaling/InitiatorSignaling.java
Line 403 in d01e553
We set the state to TOKEN_RECEIVED for every new responder before they send us any message.
Hence as long as I didn't overlook anything we won't ever drop any old responders as we assume we got
valid token message from all of them.
The text was updated successfully, but these errors were encountered: