nnrpd doesn't support passwords with spaces

[eagle]

The NNTP protocol uses whitespace as a command and argument separator, which means that passwords containing whitespace don't work. The generic NNTP parser in nnrpd throws away the tail end of the password or produces a syntax error.

However, since the password is the last argument, we can hack around this problem. Here's a patch from Jeffrey M. Vinocur from 2001 that implements that fix, which may require some updating.

[eagle]

Replacement misc.c with new Argify()

[eagle]

Patch to make nnrpd use new Argify()

[Julien ÉLIE]

(In [8269]) RFC 4643 states that usernames and passwords can contain spaces.
More generally, they are bytes strings (without NUL, CR and LF).

Now that AUTHINFO SASL is implemented, nnrpd supports that.
This patch fixes the decoding of the news.notice file: innreport
couldn't see usernames with spaces.

Also see #30 (for AUTHINFO USER/PASS where both usernames
and passwords could contain spaces).

[Julien ÉLIE]

(In [8674]) Add support for whitespaces in usernames/passwords provided
with AUTHINFO USER/PASS. nnrpd was previously considering
as invalid passwords like "a b" (two arguments "a" and "b"
when only one was expected) or parsing " ab" as "ab"
(stripping the leading space).

nnrpd now treats everything after the first whitespace
character following AUTHINFO USER/PASS, up to, but not
including, the CRLF, as the username/password.

Thanks to Jeffrey M. Vinocur for the initial patch.

close #30