Sorry, no, it's too late to get this into 1.1
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4410
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Sorry for no documentation.
In SRP6a, after the client and server calculate a common session key, they must
prove to each other that their keys are idential to finish authentication.
That is client send the M1, and server verifies M1 and responses with M2, then
client verifies M2.
I notice that
We need a little more explanation.
Is this a new feature? Being added to 1.0.2? (That won't be accepted, only
fixes go into released branches.) Or is this something that was dropped and
should be restored?
Unfortunately, the 1.1 freeze deadline is in 24 hours. This won't make it into
1.1
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4410
Please log in as guest with password guest if prompted
add_srp_m1_m2.patch
Description: Binary data
add_srp_m1_m2.patch
Description: Binary data
--
openssl-dev mailing list
To unsubscribe:
