Re: [Noffle-users] AUTHINFO SIMPLE with noffle ?

[Jim H. <jim...@ac...>]

On 10-Feb-2003 Dominique Dumont wrote:
> With noffle v 1.1.3, I want to connect to a news server with
> authentification. But it looks like this server cannot accept
> AUTHINFO:
> 
>   [S] AUTHINFO USER dumont
>   [S FLUSH]
>   [R] 381 PASS required
>   Username rejected. Server stat: 381 PASS required
> 
> According to this server's doc, I should use the 'authinfo simple
> USERNAME PASSWORD'
> 
> So is there a way to setp up noffle so that a 'authinfo simple'
> command is used instead of 'AUTHINFO USER' ?

Unfortunately, not at the moment. It would be simple to implement, but I
haven't done so for 2 reasons:

1. Nobody ever asked :-)
2. The latest IETF recommendations say that this should not be implemented.
   However, since we're talking here about a client, not a server, I think
   it would be OK to implement. 

However, looking at the above, I'm confused. The upstream server does seem to
be returning '381' to the AUTHINFO USER. '381' is the correct 'send me the
password' response, so Noffle *should* have then sent AUTHINFO PASS. But it
didn't, for some reason. Hang on, I'll check the code...

<Blink>

Aarrgghh! There's a horrid cockup in client.c! And, to my shame, I also now see
there's a patch waiting on SourceForge for it.

The fix is to change STAT_AUTH_REQUIRED on line 169 of client.c to
STAT_MORE_AUTH_REQUIRED.

I've now done this in CVS. This is, I think, sufficient breakage to justify a
1.1.4 release as soon as I can get round to it.

-- 
Jim Hague - jim...@in... (Work), ji...@be... (Play)
Never trust a computer you can't lift.