search for: rfc3066

...--------------------------------------------- 11. Additional Messages Either party may send any of the following messages at any time. 11.1 Disconnection Message byte SSH_MSG_DISCONNECT uint32 reason code string description [RFC3629] string language tag [RFC3066] This message causes immediate termination of the connection. All implementations MUST be able to process this message; they SHOULD be able to send this message. The sender MUST NOT send or receive any data after this message, and the recipient MUST NOT accept any data after recei...

...74 0x65 0x64 0x20 0x62 0x79 0x20 0x75 0x73 0x65 0x72 Is this not incomplete? In RFC 4253, section 11.1, the payload for this message is defined to be uint32 reason code string description in ISO-10646 UTF-8 encoding [RFC3629] string language tag [RFC3066] Is it the case that if the sender does not want to use a language tag it can omit the language string altogether, or must one still send an empty string - i.e. a sequence of four bytes all set to zero?

...this by responding with SSH_MSG_USERAUTH_PASSWD_CHANGEREQ. In any case the server MUST NOT allow an expired password to be used for authentication. byte SSH_MSG_USERAUTH_PASSWD_CHANGEREQ string prompt in ISO-10646 UTF-8 encoding string language tag as defined in [RFC3066] ... </snip> I tested with the OpenBSD ssh client and portable ssh in cygwin. It specifically doesn't send the language tag. Here is the tail of ssh -vvv, <snip> debug1: Next authentication method: password debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64) debug2: w...

https://bugzilla.mindrot.org/show_bug.cgi?id=2058 Bug ID: 2058 Summary: SSH Banner message displays UTF-8 multibyte char incorrrectly Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5