[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: |
Michael Albinus |
Subject: |
bug#49723: 28.0.50; Test in coding.c for NUL bytes in filenames is not reliable |
Date: |
Thu, 16 Sep 2021 20:44:32 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> > +** '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?
>
> Are we sure remote file names cannot include null bytes?
Likely not. I have added "foo\0bar" as file name in tramp-test.el, and
then I get
--8<---------------cut here---------------start------------->8---
Test tramp-test41-special-characters condition:
(ert-test-failed
((should
(file-exists-p file1))
:form
(file-exists-p "/mock:gandalf:/tmp/tramp-testkLeKOx/foo\0bar")
:value nil))
FAILED 1/1 tramp-test41-special-characters (0.484141 sec)
--8<---------------cut here---------------end--------------->8---
Well, perhaps Tramp can be improved to handle null bytes on (remote)
shell level, but do we need this?
Best regards, Michael.
- 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 <=
- 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, 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