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] [day] [month] [year] [list]
Date:   Tue, 3 Mar 2020 09:48:50 +0800
From:   lampahome <pahome.chen@...lab.org>
To:     Aleksa Sarai <cyphar@...har.com>
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: why do we need utf8 normalization when compare name?

> Sorry, a better example would've been "ñ" (U+00F1). You can also
> represent it as "n" (U+006E) followed by "◌̃" (U+0303 -- "combining
> tilde"). Both forms are defined by Unicode to be canonically equivalent
> so it would be incorrect to treat the two Unicode strings differently
> (that isn't quite the case for "Å").

So utf8-normalize will convert  "ñ" (U+00F1) and "n" (U+006E) followed
by "◌̃" to a utf8 code, and both are the same, right?
Then compare it byte by byte.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ