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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Mar 2015 21:21:06 +0100
From: CodesInChaos <>
Subject: Re: [PHC] NFC v NFD UTF-8 Normalization Re: [Was output specifics]

I also recommend Form C, since that's the form most text is in if you
apply no normalization. That way you maximize interoperability with
implementations that don't bother with normalization. UTF-8 and no BOM
are obvious choices as well.

On Wed, Mar 11, 2015 at 7:42 PM, Thomas Pornin <> wrote:
> generality. For instance, the switched-case equivalent of "sTRASSE" can
> be either "Straße" and "Strasse"

I think in this case we want the caps-lock switched equivalent, which
is a question mark `?` for `ß` on the German keyboard layout.

Powered by blists - more mailing lists