andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
10,329 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
00fd4ea264
Go to file
Norman Maurer 00fd4ea264
Disable TLSv1 and TLSv1.1 by default (#11237) 
Motivation:

TLSv1 and TLSv1.1 is considered insecure. Let's follow the JDK and disable these by default

Modifications:

- Disable TLSv1 and TLSv1.1 by default when using OpenSSL.
- Add unit tests

Result:

Use only strong TLS versions by default when using OpenSSL
2021-05-11 10:43:40 +02:00
.github
.mvn
all
bom
buffer
codec
codec-dns
codec-haproxy
codec-http
codec-http2
codec-memcache
codec-mqtt
codec-redis
codec-smtp
codec-socks
codec-stomp
codec-xml
common Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
dev-tools
docker
example
handler Disable TLSv1 and TLSv1.1 by default (#11237) 2021-05-11 10:43:40 +02:00
handler-proxy
license
microbench
resolver
resolver-dns
resolver-dns-native-macos Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
scripts
tarball
testsuite Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
testsuite-autobahn
testsuite-http2
testsuite-native
testsuite-native-image
testsuite-native-image-client
testsuite-native-image-client-runtime-init
testsuite-osgi
testsuite-shading
transport
transport-blockhound-tests
transport-native-epoll Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
transport-native-kqueue Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
transport-native-unix-common
transport-native-unix-common-tests
transport-rxtx
transport-sctp
transport-udt Use PlatformDependent#normalizedOs() instead of reading os.name prop (#11239) 2021-05-11 08:52:29 +02:00
.fbprefs
.gitattributes
.gitignore
.lgtm.yml
CONTRIBUTING.md
LICENSE.txt
mvnw
mvnw.cmd
nohttp-checkstyle-suppressions.xml
nohttp-checkstyle.xml
NOTICE.txt
pom.xml Update conscrypt and add workaround for test failure (#11238) 2021-05-11 10:40:54 +02:00
README.md
run-example.sh
SECURITY.md

README.md

Build project

Netty Project

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

Links

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+ / 4.1+) 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.1 resides in the branch '3.9' and the branch '4.1' respectively.

Usage with JDK 9+

Netty can be used in modular JDK9+ applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.all
  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.