Re: use of the term "verifier" with SCRAM
| От | Peter Eisentraut |
|---|---|
| Тема | Re: use of the term "verifier" with SCRAM |
| Дата | |
| Msg-id | e7b54a17-462e-4308-e2a0-1edb788e0067@2ndquadrant.com обсуждение |
| Ответ на | Re: use of the term "verifier" with SCRAM (Michael Paquier <michael@paquier.xyz>) |
| Список | pgsql-hackers |
On 2019-10-10 10:03, Michael Paquier wrote: > On Thu, Oct 10, 2019 at 09:08:37AM +0200, Peter Eisentraut wrote: >> Here is my proposed patch to adjust this. > > Looks fine to me reading through. I think that you are right to not > change the descriptions in build_server_final_message(), as that's > described similarly in RFC 5802. committed > By renaming scram_build_verifier() > to scram_build_secret() you are going to break one of my in-house > extensions. I am using it to register for a user SCRAM veri^D^D^D^D > secrets with custom iteration and salt length :) OK, that should be easy to work around with an #ifdef or two. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: