linux-kernel - Re: [patch] Makefile: Unexport LANG

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]

Message-ID: <20100108004117.GK2436@verge.net.au>
Date:	Fri, 8 Jan 2010 11:41:18 +1100
From:	Simon Horman <horms@...ge.net.au>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Masami Hiramatsu <mhiramat@...hat.com>,
	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
	Michal Marek <mmarek@...s.cz>,
	Roland Dreier <rdreier@...co.com>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [patch] Makefile: Unexport LANG

On Sat, Dec 26, 2009 at 10:20:07PM +1100, Simon Horman wrote:
> On Fri, Dec 25, 2009 at 09:14:40PM -0800, H. Peter Anvin wrote:
> > On 12/25/2009 08:30 PM, Masami Hiramatsu wrote:
> > >>  
> > >>  # Avoid funny character set dependencies
> > >> +unexport LANG
> > >>  unexport LC_ALL
> > >>  LC_CTYPE=C
> > >>  LC_COLLATE=C
> > > 
> > 
> > At this point, it seems to me that we should just LC_ALL=C and be done
> > with it (see other thread.)
> 
> Sure, that would also work for the case that I'm seeing.
> 
> I tested the following:
> 
> # Avoid funny character set dependencies
> LC_ALL=C
> export LC_ALL
> 
> Though personally I would advocate tweaking the locale as needed closer
> to awk scripts and the like, rather than the high-level general change that
> was made. Fall-out from a high-level change seems inevitable to me.

This seems to still be broken. Can we decide on a solution?


--
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/