On Sun, Feb 19, 2017 at 6:55 PM, Robert Haas <robertmh...@gmail.com> wrote: > Gosh, this SCRAM stuff seems to be taking us pretty deeply into > dealing with encoding details which apparently we haven't formerly > needed to worry about. That is a little surprising and maybe > something we should try to avoid?
The RFC of SCRAM, RFC5802 is clear on the matter (https://tools.ietf.org/html/rfc5802), SASLprep needs NFKC (RFC4013 here, the worst in the set https://tools.ietf.org/html/rfc4013) if we want our implementation to be compatible with any other Postgres driver that implement things at protocol level without libpq. I think that JDBC is one of those things. So I am afraid we cannot avoid it if we want SCRAM. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
