ietf-nntp AUTHINFO SASL protocol choices

[Lawrence Greenfield]

On the contrary, since the SASL exchange will require a line length of
greater than 85000 characters, it makes perfect sense to special case
the authentication command to do dynamic memory allocation up to 85k
but not allow other commands to create such memory demands.

Larry

   From: Russ Allbery <rra at stanford.edu>
   Organization: The Eyrie
   Date: Thu, 28 Mar 2002 10:41:57 -0800

   Charles Lindsey <chl at clw.cs.man.ac.uk> writes:

   > It would require great skill to write an implementation that would
   > accept 1024 octets for the BLAH command, but would fail to accept 1024
   > octets for all other commands.

   Not really; it would just require a poor design.  :)  Think, for example,
   of an old server onto which was tacked a SASL authentication handler that
   was completely separte; when it gets the AUTHINFO command, it hands off
   the connection to the SASL handler, which does its thing, sets some
   variables, and then hands back to the rest of the code.

   It's quite possible for some implementation strategies to result in that
   situation, but those aren't implementation strategies that I'd recommend
   to anyone.

   -- 
   Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>
   _______________________________________________
   ietf-nntp mailing list
   ietf-nntp at academ.com
   https://www.academ.com/mailman/listinfo/ietf-nntp