[dolphin] [Bug 414478] User Should definitely be warned every time an Invalid filename is used!
myusualnickname at gmail.com
myusualnickname at gmail.com
Sun Apr 28 02:09:50 BST 2024
https://bugs.kde.org/show_bug.cgi?id=414478
myusualnickname at gmail.com <myusualnickname at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |myusualnickname at gmail.com
--- Comment #7 from myusualnickname at gmail.com <myusualnickname at gmail.com> ---
It looks like a forward slash, but it is a replacement look alike character
that we cannot type.
I filed a bug for that in kde 4 but the bug was marked invalid because someone
was proud of breaking our systems... adding a feature that they thought was
cool.
It is worse than that, Case preserving case insensitive filesystems can clobber
data if a new filename is made differing only by case.
It is worse than that, filenames can be anything other than null and forward
slash. So the escape sequence that messes with terminals can be sent. Ever
cat a binary file and have your terminal get messed up? Well, we're living
with a huge vulnerability in files like that.
Dolphin should flag files with harmful characters. Basically there should be a
test to see if a file name is valid unicode, and then check for a list of
banned characters. I would like this in the device driver/filesystem level on
the system, but it requires communication with the user space. Creating a file
with the same name but different case should cause a problem.
This is a very severe problem that people just ignore.
(In reply to witchhunter from comment #5)
> TIL things are even worse.
> Dolphin clearly allows you to create a filename containing '/' (forward
> slash) on EXT4.
> 1) Don't know what is the reasoning behind this witchcraft but this is only
> doing more harm than good.
> 2) With all due respect to KDE devs, but don't they show the same upstream,
> to EXT4 founders. This is just unprofessional.
> 3) More ironically Dolphin throws nice warning when you try to name a
> directory containing the forward slash sign. This is plane inconsistency.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list