linux-kernel - Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH

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:	Sat, 02 May 2009 21:48:24 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	tridge@...ba.org
Cc:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>,
	Steve French <sfrench@...ibm.com>,
	Mingming Cao <cmm@...ibm.com>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH] Add CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES option

tridge@...ba.org writes:

>  > Ah. What is the intent to force WINNT option (lcase field)? To force it
>  > may not be good. So, change default if config is on?
>
> The idea behind forcing it is that it maintains maximum
> functionality without the user having to use special mount
> options. For example, if a Linux user creates a file "README.txt" then
> the name will be preserved exactly, whereas without that hackery it
> becomes README.TXT on disk.
>
> It does mean we are mixing up two things with that config option
> though, which is why I asked you about it. Would you prefer to just
> let the distros worry about the default mount options when someone
> plugs in a VFAT device on a system with
> CONFIG_VFAT_NO_CREATE_WITH_LONGNAMES set? 

I see.

> Or maybe we should change the defaults in parse_options() when this
> option is set?

Current default (shortname=lower) is just for historically reason.
Personally, I'm thinking it's not good as default ("winnt" or "mixed" is
prefer).

Anyway, I'm not sure though, I guess to change the default is good than
force it at least, because it would be the user policy.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
--
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/