[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not r
From: |
Federico Tedin |
Subject: |
bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable |
Date: |
Thu, 16 Sep 2021 20:38:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Michael Albinus <michael.albinus@gmx.de> writes:
> Federico Tedin <federicotedin@gmail.com> 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.
Would this imply only doing it in `tramp-handle-expand-file-name`, or
other functions as well?
I had thought of doing it for at least `tramp-handle-expand-file-name`,
but then I noticed that the function eventually calls `expand-file-name`
with a combination of name + dir, or only with name. So in that case I
figured that the null bytes check would be performed by
`expand-file-name` anyways.
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/14
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/14
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/14
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Michael Albinus, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Michael Albinus, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable,
Federico Tedin <=
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Michael Albinus, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/16
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Michael Albinus, 2021/09/20
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/17
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/17
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Eli Zaretskii, 2021/09/18
- bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable, Federico Tedin, 2021/09/18