> On Oct 11, 2016, at 9:14 AM, Emmanuel Lécharny <[email protected]> wrote: > > Yes, to cover all the chars a password may content. But you may also > make it so that the password only contains valid chars (ie, some that > can be stored in a String without being invalid), avoiding this hex > representation.
What’s going on here is we’ve uncovered a 2nd problem (pw values), independent of the 1st (pw datatypes). The 2nd problem dictates we support password values in an expanded character set encompassing anything that can be carried in a String of 2 byte hex. It’s an important consideration that I didn’t see so thanks for bringing it up. But, it needs to be handled separately. We’ll need two tickets. Speaking of, here’s the first: https://issues.apache.org/jira/browse/FC-194 That work has already been committed to trunk. Shawn
