Subject: Re: bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable

From: Michael Albinus <[email-masked]>
Date: Thu, 16 Sep 2021 20:12:09 +0200

Federico Tedin <[email-masked]> writes:

Hi,

Sorry for being late, I have seen this just now only.

> +** 'expand-file-name' now checks for null bytes in filenames.
> +The function will now check for null bytes in both NAME and
> +DEFAULT-DIRECTORY arguments, as well as in the 'default-directory'
> +buffer-local variable, assuming its value is used.  If null bytes are
> +found, 'expand-file-name' will signal an error.

Should this be implemented also in remote file names?

Best regards, Michael.