[GH-ISSUE #146] Cloak sending wrong old timestamps #120

Closed
opened 2026-02-26 12:34:02 +03:00 by kerem · 1 comment
Owner

Originally created by @notsure2 on GitHub (Dec 20, 2020).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/146

There is race condition or aliasing issue... Cloak is sending old timestamps so the handshake is getting rejected for some threads.
I will investigate and make a pull request.

Originally created by @notsure2 on GitHub (Dec 20, 2020). Original GitHub issue: https://github.com/cbeuw/Cloak/issues/146 There is race condition or aliasing issue... Cloak is sending old timestamps so the handshake is getting rejected for some threads. I will investigate and make a pull request.
kerem closed this issue 2026-02-26 12:34:02 +03:00
Author
Owner

@notsure2 commented on GitHub (Dec 21, 2020):

I am not sure, but I can't reproduce it, it may have been old connections stuck in handshake and by the time the socket data was transmitted, time had passed and the handshake wasn't valid anymore... I will reopen this issue if I catch this again.

<!-- gh-comment-id:748698575 --> @notsure2 commented on GitHub (Dec 21, 2020): I am not sure, but I can't reproduce it, it may have been old connections stuck in handshake and by the time the socket data was transmitted, time had passed and the handshake wasn't valid anymore... I will reopen this issue if I catch this again.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Cloak#120
No description provided.