Bug 描述
客户端或服务端发消息,对方收到消息后,没有发送回执,无法判断消息是否发送成功.
这是一个很大的漏洞,如果要做离线消息的话,消息是否发送成功是一个非常重要的点

In the dockerfile

https://github.com/jpillora/chisel/blob/f3a8df20e389ce41cd49101408231c67c093f5af/Dockerfile#L9-L12

Is that normal that https://github.com/jpillora/chisel/share.BuildVersion=1.3.1 returns Not found because I see it is used in the dockerfile?

Also maybe you could help us with packaging chisel in BlackArch BlackArch/blackarch#2456

1. The example configuration of tunnel.yml: indent charaters uses both tab and spaces, which makes it not parsable.
   2 After fixed 1, client throws the following error:

configuration error: tls invalid protocol "sni"

Client version: 2.1

There are newer implementations of i18n for node that allow you to define the base language in your code directly, and then provide optional override files.

This makes developing much more pleasant.

I noticed that the "certificate weakening" TlsOptions like IgnoreCertificateChainErrors, IgnoreCertificateRevocationErrors, AllowUntrustedCertificates and CertificateValidationCallback have no effect when using web socket connections.

I understand this is because the underlying api (System.Net.WebSockets) does not support this (at least not in all target frameworks), but I think it should be no

Please explain the suggested feature in detail.

Being able to use Server outside of NetworkBehaviour will make it quicker to create Server only methods. The currently you have to add a manual check for NetworkServer.active.

[Server] causes Weaver to add the following code at the start of methods, which does not depend on NetworkBehaviour.

if (!NetworkServer.active)

Please check the reproducible example here: https://github.com/michaelr524/reactor-netty-ssl-leak

mvn clean package
java -jar target/reactor-netty-ssl-leak-1.0-SNAPSHOT.jar 

• Reactor version(s) used: 0.9.4.RELEASE
• Other relevant libraries versions (eg. netty, ...):
• JVM version (javar -version):
  openjdk version "12.0.2" 2019-07-16
  OpenJDK Runtime Environment (build 12.0