…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 […

…nclude 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 password …

…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…

…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…

…d 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. Since it…

… 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…

…y forms as well as existing string representations, such as simple user names [ RFC4013 ]. Where the specification does not precisely prescribe how identities in SASL relate to identities used elsewhere in the protocol, for instance, in access control policy statements, it Melnik…

…cription of those circumstances. o Normalize(str): Apply the SASLprep profile [ RFC4013 ] of the "stringprep" algorithm [ RFC3454 ] as the normalization algorithm to a UTF-8 [ RFC3629 ] encoded "str". The resulting string is also in UTF-8. When applying SASLprep, "str" is treated…

… 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…

…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…

…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…