https://bugzilla.mindrot.org/show_bug.cgi?id=3061
--- Comment #1 from Darren Tucker <dtuc...@dtucker.net> --- FWIW since your example uses opcode 255, the current behaviour seems more in compliance with RFC4254 than the previous behaviour: https://tools.ietf.org/html/rfc4254#page-19: Opcodes 160 to 255 are not yet defined, and cause parsing to stop (they should only be used after any other data). other than that it doesn't take a strong stance on unknown opcodes: the server MAY ignore any modes it does not know about -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list openssh-bugs@mindrot.org https://lists.mindrot.org/mailman/listinfo/openssh-bugs