/ocaml-tls

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BEAST attack #2

Closed
hannesm opened this Issue Mar 3, 2014 · 3 comments

Comments

Assignees
No one assigned
Labels
Milestone
No milestone
2 participants
@hannesm @pqwy
@hannesm
Member

hannesm commented Mar 3, 2014

problem: CBC in TLS uses a static IV

solution: randomize IV by always sending an empty application data record before any with payload

references:

@hannesm hannesm added the security concern label Mar 3, 2014

@hannesm hannesm referenced this issue Mar 3, 2014

Closed

Confidence? #1

@hannesm

This comment has been minimized.

Sign in to view
Member

hannesm commented Apr 1, 2014

mitigation in #37
@hannesm

This comment has been minimized.

Sign in to view
Member

hannesm commented Apr 11, 2014

I am convinced this problem is solved in our stack. It would be great to have another pair of eyes looking over it and commenting here..

pqwy added a commit that referenced this issue May 4, 2014

@pqwy
reuse #2
a2d597b

pqwy added a commit that referenced this issue May 13, 2014

@pqwy
clean pass #2
74e557c

pqwy added a commit that referenced this issue May 29, 2014

@pqwy
clean pass #2
63349e1
@pqwy

This comment has been minimized.

Sign in to view
Contributor

pqwy commented Jul 7, 2014

Every vector of appdata records has an empty one prepended on send, in CBC.

Looks legit.

@pqwy pqwy closed this Jul 7, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment