linux-kernel - Re: Long file names in VFAT broken with iocharset=utf8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 May 2007 11:34:13 -0400
From:	"Albert Cahalan" <acahalan@...il.com>
To:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc:	arvidjaar@...l.ru, hirofumi@...l.parknet.co.jp,
	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: Long file names in VFAT broken with iocharset=utf8

On 5/8/07, Jan Engelhardt <jengelh@...ux01.gwdg.de> wrote:
> On May 8 2007 00:43, Albert Cahalan wrote:

> > Fix: the vfat driver should use the 8.3 name for such files.
>
> Or the 31-character ISO Level 1(?).

That might be appropriate for a similar problem on CD-ROM
filesystems. (when the CD is rockridge KOI8 and you want UTF-8)
It may even be appropriate for Joliet, though 8.3 may be
the better choice in that case.

It's not appropriate for vfat, HPFS, JFS, or NTFS. All of those
have built-in support for 8.3 aliases. Normally the 8.3 names
are like hidden hard links, except that deletion of either name
will wipe out the other. (same as case differences too)
So the names are there, and they should already work.
They just need to be reported for directory listings when the
long names would be too long.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/