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

Cannot connect 2 responders to initiator. #120

Open
ghost opened this issue Aug 27, 2019 · 2 comments
Open

Cannot connect 2 responders to initiator. #120

ghost opened this issue Aug 27, 2019 · 2 comments
Labels

Comments

@ghost
Copy link

ghost commented Aug 27, 2019

From Protocol:

A receiving client MUST delete all cached information about and for the other client with the identity of the id field (such as cookies and sequence numbers). The client MAY stay on the path and wait for a new initiator/responder to connect. However, the client-to-client handshake MUST start from the beginning. In addition, the client MUST notify the user application that the client with the identity id has disconnected.

from code

protected handleDisconnected(msg: saltyrtc.messages.Disconnected): void {
    this.client.emit({type: 'peer-disconnected', data: msg.id});
}
@ghost
Copy link
Author

ghost commented Aug 27, 2019

If initiator get disconnected message, and I try to connect back same or other responder I get
Signaling error: Protocol error (Invalid nonce: ValidationError: Responder 2 cookie changed)
Looks like initiator's state is not reseted

@lgrahl lgrahl added the bug label Oct 29, 2019
@lgrahl
Copy link
Member

lgrahl commented Oct 29, 2019

We are aware of this limitation but it would require significant refactoring to fix it (actually, in all clients except the one written in Rust).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant