Re: NFS4 requires UTF-8

["H. Peter Anvin" <hpa@xxxxxxxxx>]

Followup to:  <Pine.LNX.4.44.0202211315170.2542-100000@xxxxxxxxxxxxxxxxxxxxxxx>
By author:    Gaspar Sinai <gsinai@xxxxxxxxx>
In newsgroup: linux.utf8
> 
> I just browsed through RFC-3010 and I found one thing that
> bothers me and it has not been discussed yet (I think).
> 
> RFC says:
> > The NFS version 4 protocol does not mandate the use
> > of a particular  normalization form at this time.
> 
> How do we mount something that contains a precomposed
> character like:
> 
>   U+00E1 (Composed of U+0061 and U+0301)
> 
> If the U+0061 U+0301 is used and our server is assumimg U+00E1,
> can a malicious hacker set up another NFS server that has
> U+0061 and U+0301 to mount his NFS volume? I could even
> imagine very tricky combinations with Vietnamese text
> but that would be another question...
> 
> Forgive my ignorance if this was discuseed - I did not see it
> in the archives.
> 

Filenames should be matched based on binary strings.  Anything else is
fundamentally futile especially in the light of new versions, etc.
(just watch how much pain various systems who try to do just case
folding go through.)

String comparison with multilingual text is clearly a very difficult
subject.

	-hpa


-- 
<hpa@xxxxxxxxxxxxx> at work, <hpa@xxxxxxxxx> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<amsp@xxxxxxxxx>
--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/