IUTF8 Terminal Mode in Secure Shell (SSH)
RFC 8160
Document | Type |
RFC
- Proposed Standard
(April 2017)
Was
draft-sgtatham-secsh-iutf8
(individual)
|
|
---|---|---|---|
Authors | Simon Tatham , Darren Tucker | ||
Last updated | 2017-04-19 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
IESG | Responsible AD | Kathleen Moriarty | |
Send notices to | (None) |
RFC 8160
New version available: quot; defined in Section 8 of [RFC4254]. IANA has added the following opcode to the "Pseudo-Terminal Encoded Terminal Modes" registry: opcode mnemonic description ------ -------- ----------- 42 IUTF8 Terminal input and output is assumed to be encoded in UTF-8. 5. Security Considerations The security considerations of [RFC4254] apply. This additional terminal mode encoding is believed to have no security implications differing from the existing set of encoded terminal modes. Since the IUTF8 terminal mode is intended for use in conjunction with the UTF-8 character encoding, the security considerations of [RFC3629] also apply to systems in which this mode is enabled. In particular, terminal drivers that interpret this bit as enabling UTF-8-aware line-editing behavior should carefully consider how that behavior will treat illegal sequences, overlong encodings, and redundant representations of composed characters (see [UNICODE]). 6. References 6.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 2003, <http://www.rfc-editor.org/info/rfc3629>. [RFC4254] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) Connection Protocol", RFC 4254, DOI 10.17487/RFC4254, January 2006, <http://www.rfc-editor.org/info/rfc4254>. 6.2. Informative References [UNICODE] The Unicode Consortium, "The Unicode Standard", <http://www.unicode.org/versions/latest/>. Tatham & Tucker Standards Track [Page 3] RFC 8160 IUTF8 Terminal Mode in SSH April 2017 Acknowledgements The authors are indebted to Colin Watson for originally suggesting this terminal mode in 2005, and David Madore and Jakub Jelen for prior implementation efforts. Authors' Addresses Simon Tatham PuTTY Email: anakin@pobox.com Darren Tucker OpenSSH Email: dtucker@openssh.com Tatham & Tucker Standards Track [Page 4]