Sam Hartman wrote: > This isn't a bad idea. Think though about how it interacts with > password databases used for multiple purposes. You sometimes get into > situations where you need to do normalization both at the client and > server. That too can be OK. You just need to think it all through > when writing your specs.
When people enter passwords, the pop-up window often says "CASE SENSITIVE", and "Make sure you don't have CAPS-LOCK pressed". Servers don't currently normalize passwords to do case-insensitive comparisons. I don't see why they would need to normalize passwords for composed/decomposed characters. Alan DeKok. _______________________________________________ Emu mailing list [email protected] https://www1.ietf.org/mailman/listinfo/emu
