From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Joseph D. Wagner" <theman@josephdwagner.info>
Subject: RE: RFC: Illegal Characters in File Names
Date: Mon, 19 Jul 2004 15:54:05 -0500
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <S263100AbUGSUyJ/20040719205409Z+827@vger.kernel.org>
References: <6C290390-D9BF-11D8-8075-00039398BB5E@ieee.org>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc: <linux-fsdevel@vger.kernel.org>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from ssa8.serverconfig.com ([209.51.129.179]:55018 "EHLO
	ssa8.serverconfig.com") by vger.kernel.org with ESMTP
	id S263100AbUGSUyJ (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Mon, 19 Jul 2004 16:54:09 -0400
To: "'Pat LaVarre'" <p.lavarre@ieee.org>
In-Reply-To: <6C290390-D9BF-11D8-8075-00039398BB5E@ieee.org>
List-Id: linux-fsdevel.vger.kernel.org

> unicode.org speaks of the security issues implicit in multiple byte
> encodings of the same char.  Those remain even after a ban on '\b'.

I can't find it.  Please provide a link.

Joseph D. Wagner