commit | 9f53229c2ac97dbc6f5a03657de08a1150a9ac7e | [log] [tgz] |
---|---|---|
author | djm@openbsd.org <djm@openbsd.org> | Tue Sep 12 06:35:31 2017 +0000 |
committer | Damien Miller <djm@mindrot.org> | Tue Sep 12 17:37:03 2017 +1000 |
tree | 4f74dc06676dc6dce2b2bc3aa6beb248a1d8def6 | |
parent | dbee4119b502e3f8b6cd3282c69c537fd01d8e16 [diff] |
upstream commit Make remote channel ID a u_int Previously we tracked the remote channel IDs in an int, but this is strictly incorrect: the wire protocol uses uint32 and there is nothing in-principle stopping a SSH implementation from sending, say, 0xffff0000. In practice everyone numbers their channels sequentially, so this has never been a problem. ok markus@ Upstream-ID: b9f4cd3dc53155b4a5c995c0adba7da760d03e73