…uch mechanisms is a "simple user name" (see Section 2 of [RFC4422] as well as [ RFC4013 ]). Various application technologies also assume that the identity of a user or account takes the form of a username (e.g., authentication for the Hypertext Transfer Protocol as specified in […

…clude the USER argument in the UTF8 capability response SHOULD apply SASLprep [ RFC4013 ] to the arguments of the USER and PASS commands. A client or server that supports APOP and permits UTF-8 in user names or passwords MUST apply SASLprep [ RFC4013 ] to the user name and passwo…

…clude the USER argument in the UTF8 capability response SHOULD apply SASLprep [ RFC4013 ] to the arguments of the USER and PASS commands. A client or server that supports APOP and permits UTF-8 in user names or passwords MUST apply SASLprep [ RFC4013 ] to the user name and passwo…

… sequence of less than 513 bytes, and MUST have been processed using SASLprep [ RFC4013 ]. 15.4 . MESSAGE-INTEGRITY The MESSAGE-INTEGRITY attribute contains an HMAC-SHA1 [ RFC2104 ] of the STUN message. The MESSAGE-INTEGRITY attribute can be present in any STUN message type. Sinc…

… sequence of less than 513 bytes, and MUST have been processed using SASLprep [ RFC4013 ]. 15.4 . MESSAGE-INTEGRITY The MESSAGE-INTEGRITY attribute contains an HMAC-SHA1 [ RFC2104 ] of the STUN message. The MESSAGE-INTEGRITY attribute can be present in any STUN message type. Sinc…

…uthentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely transition to the use of PRECIS-based handling rules as specified in [ RFC7613 ]. For a detailed…

…SSH implementations that both store the passwords and compare them SHOULD use [ RFC4013 ] for normalization. Note that even though the cleartext password is transmitted in the packet, the entire packet is encrypted by the transport layer. Both the server and the client should che…

…authentication. At the time of this writing, some SASL mechanisms use SASLprep [RFC4013] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely transition to the use of PRECIS-based handling rules as specified in [RFC7613]. For a detailed di…

…uthentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely transition to the use of PRECIS-based handling rules as specified in [ RFC7613 ]. For a detailed…

…uthentication. At the time of this writing, some SASL mechanisms use SASLprep [ RFC4013 ] for the handling of usernames and passwords; in the future, these SASL mechanisms will likely transition to the use of PRECIS-based handling rules as specified in [ RFC7613 ]. For a detailed…

…ument. In particular, the security considerations in RFC 3454 RFC 3629 RFC 4013 RFC4013 ], and RFC 5890 go into a fair amount of detail. 10 . References 10.1 . Normative References ISOIEC10646 ] ISO/IEC, "ISO/IEC 10646:2011. International Standard -- Information technology - Univ…

…a consequence of SASLprep which contains (https://datatracker.ietf.org/doc/html/rfc4013#section-2.1): "the "commonly mapped to nothing" characters [StringPrep, B.1] that can be mapped to nothing.". the "commonly mapped to nothing" list in https://datatracker.ietf.org/doc/html/rfc…

…a consequence of SASLprep which contains (https://datatracker.ietf.org/doc/html/rfc4013#section-2.1): "the "commonly mapped to nothing" characters [StringPrep, B.1] that can be mapped to nothing.". the "commonly mapped to nothing" list in https://datatracker.ietf.org/doc/html/rfc…