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.

Sign up for GitHub

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

Jump to bottom

TlsHandler negotiates wrong protocols on server side #89

Closed
nayato opened this issue Apr 27, 2016 · 0 comments
Closed

TlsHandler negotiates wrong protocols on server side #89

nayato opened this issue Apr 27, 2016 · 0 comments
Assignees
@nayato
Labels
bug

Comments

@nayato
Copy link
Member

nayato commented Apr 27, 2016

TlsHandler negotiates TLS 1.0 and SSL 3.0 only (defaults in .NET Framework).
@nayato nayato mentioned this issue Apr 27, 2016
Merged
nayato added a commit to nayato/DotNetty that referenced this issue Apr 27, 2016
@nayato
Fixes ByteBuffer+Stream integration, TLS neg, STEE Shutdown
aa3cbc6 
Motivation:
Fix up top priority issues to ensure proper working state with recent changes.

Modifications:
- TlsHandler negotiates TLS 1.0+ on server side (Azure#89)
- STEE properly supports graceful shutdown (Azure#7)
- UnpooledHeapByteBuffer.GetBytes honors received index and length (Azure#88)
- Echo E2E test uses length-prefix based framing (Azure#90)

Result:
Setting up DotNetty does not require workarounds for shutdown and hacks to enable negotiation of higher versions of TLS. Tests are passing even with new SslStream behavior.
@nayato nayato added the bug label Apr 27, 2016
@nayato nayato self-assigned this Apr 27, 2016
@nayato nayato closed this as completed Apr 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nayato nayato

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nayato