linux-kernel - Re: [PATCH] Sanitize filesystem NLS handling

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:	Thu, 22 Mar 2007 01:50:33 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	"Alexander E. Patrakov" <patrakov@....usu.ru>
Cc:	LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>,
	agalakhov@...lrs.uran.ru, Kay Sievers <kay.sievers@...y.org>
Subject: Re: [PATCH] Sanitize filesystem NLS handling

"Alexander E. Patrakov" <patrakov@....usu.ru> writes:

> Would it be OK for you if I add the mount-time check for iocharset=utf8 to 
> the fat filesystem and silently replace this with the "utf8" option, instead 
> of overly actively warning the users? This way, the sysfs option and the 
> nls_base.iocharset module parameter will still work as I want.

Sounds good. But, how do you specify the iocharset's nls for utf8?

>> Because you didn't change the locale. And it is your policy, right?
>
> Yes. This is because I have some files with non-ASCII names in my home 
> directory. Changing the locale would make these filenames look wrong until I 
> change it back.

The _kernel_ has no reason to force one policy, and that's why I
suggested to add per-filesystem driver option (not per-super_block).
(e.g. nls provides interface for it, etc...)
-- 
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/