Reputation
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 6
Newest
 Editor
Impact
~7k people reached

  • 0 posts edited
  • 0 helpful flags
  • 6 votes cast
May
24
comment Why does TLS do Authenticate-then-Encrypt instead of Encrypt-then-Authenticate?
So, basically, it really is a case of "someone standardized it like this and they never got around to changing it because of backwards compatibility". Figured as much, but good to have it confirmed. Thanks!
May
24
comment Why does TLS do Authenticate-then-Encrypt instead of Encrypt-then-Authenticate?
I re-read the question and noticed that this was indeed not very clear. I have updated it to make this more obvious.
May
24
comment Why does TLS do Authenticate-then-Encrypt instead of Encrypt-then-Authenticate?
I think you misunderstood the question. I was referring to the actual operation of the protocol after the handshake has finished, and the order in which the encrypted content of the connection is encrypted and authenticated. You seem to be talking about the handshake protocol itself.
Dec
10
comment Proving the semantic security of the One Time pad
Okay, so, to sum up your answer: there is no explicit proof for the semantic security, because we have already proven the shannon security, which is a stronger requirement and implies semantic security.
Feb
14
comment Why is triple-DES using three different keys vulnerable to a meet-in-the-middle-attack?
@owlstead Thanks for the Link. I would never use 3DES anyway, this was just a question raised and not answered by the Wikipedia article.
Feb
14
comment Why is triple-DES using three different keys vulnerable to a meet-in-the-middle-attack?
Thanks for your answer, but the question I was trying to ask is why Meet in the Middle won't work (or will not make the attack "cheaper") on 2 keys as opposed to three keys. Or is 114 operations a fixed value for meet-in-the-middle? EDIT: Seeing your edit, it now is a bit clearer to me what you mean. Thanks.