[issue10284] NNTP should accept bytestrings for username and password

Changes by Antoine Pitrou : -- resolution: invalid -> stage: committed/rejected -> needs patch status: closed -> open title: Exception raised when decoding NNTP newsgroup descriptions -> NNTP should accept bytestrings for username and password ___ P

[issue10284] NNTP should accept bytestrings for username and password

R. David Murray added the comment: What I meant by saying that the spec was broken is that the user is going to be typing the password at a keyboard. The keyboard will generate scan codes. Those scan codes will get interpreted through a system-specific chain of processes until some bytes or

[issue10284] NNTP should accept bytestrings for username and password

Julien ÉLIE added the comment: OK, I understand. I believe it works fine in practice, because people often use ASCII-only characters... I assume it is going to be a problem when the passwords contain 8-bit characters. I doubt it will work fine if I use different news readers on different lo

[issue10284] NNTP should accept bytestrings for username and password

Julien ÉLIE added the comment: I quote what Russ Allbery has just answered on news.software.nntp: It's completely unspecified what encoding to use for AUTHINFO USER/PASS, which is one of the problems fixed by SASL. Clients should always use SASL where possible because of things like this. No

[issue10284] NNTP should accept bytestrings for username and password

Changes by STINNER Victor : -- components: +Unicode nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10284] NNTP should accept bytestrings for username and password

Changes by Hynek Schlawack : -- nosy: +hynek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue10284] NNTP should accept bytestrings for username and password

Julien ÉLIE added the comment: RFC 4616 about SASL PLAIN: The mechanism consists of a single message, a string of [UTF-8] encoded [Unicode] characters, from the client to the server. The client presents the authorization identity (identity to act as), followed by a NUL (U+) cha

[issue10284] NNTP should accept bytestrings for username and password

Antoine Pitrou added the comment: Hello Julien, > That's one of the reasons why AUTHINFO SASL is better than AUTHINFO > USER. It also allows whitespaces (a few news servers do not parse > well whitespaces in user names or passwords after AUTHINFO USER/PASS > -- imagine " test" with a leading s