Client newkeys was not always resetting the sequence counter
Dependencies
- [2]
32GIIFWRFixing strict mode - [3]
BRDS7STAAdding method `send_channel_msg` to client::Session, to make it easier to write handlers - [4]
FT67GGO4Version bump (Pijul and Thrussh) - [5]
2VTUKRLJVersion - [6]
E2SB74SVVersion 0.30.3 - [7]
7Y2ROIVZVersion bump - [8]
634OYCNMTokio 0.3 - [9]
662ZS5JFVersion 0.33.2 - [10]
VYDCQWSFVersion 0.30.6 - [11]
PDTFLA4YVersion 0.30.7 - [12]
CQSPFH4HVersion 0.30.4 - [13]
2WEO7OZLVersion updates: getting rid of anyhow + moving to Tokio 1.0 - [14]
ORSEEVB5Version bump - [15]
DJT33BQEVersion bump - [16]
WXZWQLGLCorrect negotiation without OpenSSL - [17]
OQZGSEWMBuffering non-kex packets received after issuing a KEXINIT - [18]
7FRJYUI6Reboot because of a bad change - [19]
G3FNNIIULimiting the amount of messages that can be buffered while rekeying to two channel windows - [20]
2Q3SZY2CVersion bump - [21]
ASD7JVBEDo not read past the size of the buffer (after Tokio 0.3) - [22]
CWHVPLXNVersion bump - [23]
D6H7OWTTFixing the terrapin attack mitigation - [24]
EZTTZ6OWFixing terrapin, again - [25]
TFYJ3P2AVersion 0.30.8/0.19.4, and solving conflicts
Change contents
- edit in thrussh/src/client/mod.rs at line 1154
if session.common.write_buffer.strict {session.common.write_buffer.seqn = std::num::Wrapping(0);} - replacement in thrussh/Cargo.toml at line 5
version = "0.35.4"version = "0.35.5"