Go to file
Scott Mitchell ccecc20124 Remove remote initiated renegotiation support
Motivation:
We recently removed support for renegotiation, but there are still some hooks to attempt to allow remote initiated renegotiation to succeed. The remote initated renegotiation can be even more problematic from a security stand point and should also be removed.

Modifications:
- Remove state related to remote iniated renegotiation from OpenSslEngine

Result:
More renegotiation code removed from the OpenSslEngine code path.
2018-01-15 11:13:39 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
buffer Introduce ObjectCleaner and use it in FastThreadLocal to ensure FastThreadLocal.onRemoval(...) is called 2017-12-21 07:35:13 +01:00
codec [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
common FastThreadLocal#set remove duplicate isIndexedVariableSet call 2017-12-22 09:42:12 -08:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
handler Remove remote initiated renegotiation support 2018-01-15 11:13:39 +01:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
testsuite Remove remote initiated renegotiation support 2018-01-15 11:13:39 +01:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
transport [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-12-08 14:30:35 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:53:28 +02:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:32:36 +01:00
pom.xml Test output should include GC details 2017-12-22 19:31:33 +01:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:50:53 +02:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

Development of all versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.