Skip to content
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

DHE_RSA and AES-GCM #15

Merged
merged 19 commits into from
Jun 20, 2015
Merged

DHE_RSA and AES-GCM #15

merged 19 commits into from
Jun 20, 2015

Conversation

tomato42
Copy link
Member

@tomato42 tomato42 commented Jun 10, 2015

Implementation of DHE_RSA and AES-GCM with assorted fixes.


This change is Reviewable

Adapted from a Chromium patch. This matches the other messages; __init__
gets passed parameters necessary to determine the behavior of parse
(version, cipherSuite), while the fields for outgoing messages are set
in create.
From Chromium. If an abrubt close happens while we're in the middle of
writing data, don't invalidate the session.
Client auth now participates in signature algorithms. Test-wise, this
was already covered by test 14, but since both sides implemented it
wrong the test passed. Add a test at TLS 1.1 so coverage of the
hash-less codepath isn't lost.

From Chromium.
@tomato42 tomato42 added this to the v0.5.0 milestone Jun 10, 2015
@tomato42 tomato42 force-pushed the chromium-patches-3-fixed-up branch from bc4ab52 to d5a55e5 Compare June 13, 2015 13:07
@landscape-bot
Copy link

Code Health
Repository health decreased by 0.24% when pulling d5a55e5 on chromium-patches-3-fixed-up into 1682385 on master.

tomato42 and others added 12 commits June 20, 2015 15:15
Since we're checking on server side, we need to check for
client certificate, not our (server) certificate
Enabling any faults just no-ops the handshake right now, so those tests
so they were meaningless. The tests with the assert() lines were passing
only because a bare expect will catch everything, including
AssertionError.
Adapted and then rewritten from part of a Chromium patch. Adds a test
which uses a Fault which disables this check on either peer.
Since it's safer to include what we know than the other way
round, change the filter to output only ciphers we know

includes test coverage for the method
no logic changes, just make the methods static
@tomato42 tomato42 force-pushed the chromium-patches-3-fixed-up branch from d5a55e5 to 7614023 Compare June 20, 2015 15:56
@landscape-bot
Copy link

Code Health
Repository health increased by 0.47% when pulling 7614023 on chromium-patches-3-fixed-up into 1682385 on master.

@landscape-bot
Copy link

Code Health
Repository health increased by 0.63% when pulling 1f4047d on chromium-patches-3-fixed-up into 1682385 on master.

tomato42 added a commit that referenced this pull request Jun 20, 2015
@tomato42 tomato42 merged commit 4464125 into master Jun 20, 2015
@tomato42 tomato42 deleted the chromium-patches-3-fixed-up branch June 20, 2015 16:51
@nmav nmav self-assigned this Aug 1, 2017
@nmav nmav removed their assignment Aug 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants