Re: [hybi] Handshake was: The WebSocket protocol issues.

[Roderick Baier <[e-mail]>]

Maciej Stachowiak schrieb:
> 
> Another possible strengthening is to design the actual message framing such that it is affected by data from both the client and server parts of the handshake. Let's say the whole frame header is XOR'd with the sum of client and server nonces. Then it is impossible for the server to read frames produced by a party that didn't really participate in the handshake, and likewise makes it impossible to read frames without checking the handshake. Effectively this (lightly) encrypts frame headers so they look like random bytes if there wasn't a proper handshake. For bonus points encrypt the message bodies too, and this would shore up defense against attackers using WebSocket to talk to another protocol (since, past the handshake, their bytes would look random and not actually be controlled by them).
> 


What about XORing the whole frame with the handshake (cf. Vigenère)?
C -> S: frame xor server handshake
S -> C: frame xor client handshake

Regards
Roderick



> I don't know offhand what the perf impact would be of this kind of approach. 
> 
> I note that this ad-hoc approach starts to resemble TLS the more it has added to it, only without the years of review and deployment experience, which is why I am somewhat skeptical of heading further in this direction.
> 
> 
> Regards,
> Maciej
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> hybi mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/hybi