A proposed new class, currently in 8.1. It implements the SCRAM protocol.
The implementation has already been battle-tested in pgsql in 8.1.
Any suggestions related to functionality, interface and/or naming?
Because I like to keep the implementation of pgsql in 8.0 and 8.1 mostly in sync, I would like this class to be backported to 8.0 as well.
Stephen R. van den Berg wrote:
Any suggestions related to functionality, interface and/or naming?
On second thought: This module currently implements the client-side of these negotiations. Since there could also be a server side, maybe the methods should simply be called:
create()
client_1() server_1() client_2() server_2() client_3()
Whereas client_*() have already been implemented now, and server_*() are yet to be determined.
Stephen R. van den Berg wrote:
Stephen R. van den Berg wrote:
Any suggestions related to functionality, interface and/or naming?
Whereas client_*() have already been implemented now, and server_*() are yet to be determined.
As it turns out, the serverside is easy to implement, once you already have the client.
So, it now has become: client_1() server_1() server_2() client_2() server_3() client_3()
And, having the serverside, allows for some very nice fully-contained testsuite entries.
All committed to 8.1 as of now.
pike-devel@lists.lysator.liu.se
-
Stephen R. van den Berg