Issue644 remove hrr reconstruction

[ekr]

No description provided.

[martinthomson]

So the thing to note here is that HRR can't include extensions that you don't agree should be there. So, if extensions are present, then they have to be ones that change the ClientHello (we shouldn't define any that don't). That means the only way for HRR to be wrong is:

• no extensions (decode_error)
• unknown extension (unsupported_extension)
• extension doesn't cause a change, for instance key_share uses an unknown group, or one that already had a share

In the last case, I chose to make this an illegal_parameter alert.

And yes, if you receive a second HRR, then unexpected_message is correct (note that you missed the underscore there).

I chose to send illegal_parameter

[davegarrett]

On Tuesday, October 11, 2016 08:14:32 pm Martin Thomson wrote:

• no extensions (decode_error)

or missing_extension

[martinthomson]

I think that missing_extension would be OK, but we would hit the lower-level decode_error first, since HRR is defined with:

       Extension extensions<2..2^16-1>;