On Wed, Aug 03, 2016 at 08:30:22AM -0700, Eric Rescorla wrote:
> Folks,
>
> As promised, I've written a PR that describes the new negotiation
> syntax we discussed in Berlin. I also have prototype implementation of
> this in NSS and it's quite a bit cleaner than the previous negotiation
> design.
Folks,
As promised, I've written a PR that describes the new negotiation
syntax we discussed in Berlin. I also have prototype implementation of
this in NSS and it's quite a bit cleaner than the previous negotiation
design. I think that others have found the same thing.
https://github.com/tlswg/tl
Hi Ben,
On Tue, Aug 2, 2016 at 17:05, Benjamin Kaduk wrote:
> The next step is for someone to write proposed text that would be more clear.
> Maybe you have thoughts about how things could change?
Sure, I can give it a shot. Below is my proposal. Curious to hear your
thoughts on it. I propose sli
On Wed, Aug 3, 2016 at 8:52 AM Raja ashok wrote:
> Hi David & Steven,
>
>
>
> Here our intension is to find out buggy server which implemented a cipher
> suite support with wrong value other than specified in RFC.
>
> - If that wrong value usage in that buggy server collides with
> any r
Hi David & Steven,
Here our intension is to find out buggy server which implemented a cipher suite
support with wrong value other than specified in RFC.
- If that wrong value usage in that buggy server collides with any
real cipher suite on the period of deployment means, the bug would
