Ftp-WG: Proposed changes to MLST -15 (will be -16)

On Wed, Jul 17, 2002 at 10:54:03PM -0500, Robert Elz wrote:
>| For the data connection, no such escape
>| mechanism exists, and transmitting a file name containing
>| the <CR><LF> sequence as-is in response to MLSD is
>| guaranteed to cause trouble.
> 
> This is a different issue entirely, but it is a good point.
> Is this a problem that we need to solve?   If not, then we
> should probably at least make mention of it somewhere.

It should be addressed, but I'm not sure about the best
solution. Non-shortest UTF-8 is supposed to be illegal, so
it might be advisable to adopt parts of the NVT processing
for the MLSD data connection: transmit <NUL> after <CR>
unless that <CR> starts the regular EOL sequence.

Marc