e4mc Retro 1.0.2+1.9-1.12.2

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.9-1.12.2...1.0.2+1.9-1.12.2

e4mc Retro 1.0.2+1.8.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.8.x...1.0.2+1.8.x

e4mc Retro 1.0.2+1.7.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.7.x...1.0.2+1.7.x

e4mc Retro 1.0.2+1.16.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.16.x...1.0.2+1.16.x

e4mc Retro 1.0.2+1.15.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.15.x...1.0.2+1.15.x

e4mc Retro 1.0.2+1.14.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.14.x...1.0.2+1.14.x

e4mc Retro 1.0.2+1.13.x

Changelog

1.0.2

• Added a new configuration option: useInsecureTLS
  This allows disabling TLS certificate validation for relay connections.
  ⚠️ Warning: This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
  See this comment for detailed instructions and rationale.
• Improved TLS handling for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

Full Changelog: 1.0.1+1.13.x...1.0.2+1.13.x

e4mc Retro 1.0.1+1.16.x

Changelog

1.0.1

• Fixed a bug where commands would not output and could crash due to a NullPointerException in the sendCommandFeedback mixin when getServer() returned null.

Full Changelog: 1.0.1+1.13.x...1.0.1+1.16.x

e4mc Retro 1.0.1+1.15.x

Changelog

1.0.1

• Fixed a bug where commands would not output and could crash due to a NullPointerException in the sendCommandFeedback mixin when getServer() returned null.

Full Changelog: 1.0.1+1.13.x...1.0.1+1.15.x

e4mc Retro 1.0.1+1.14.x

Changelog

1.0.1

• Fixed a bug where commands would not output and could crash due to a NullPointerException in the sendCommandFeedback mixin when getServer() returned null.

Full Changelog: 1.0.1+1.13.x...1.0.1+1.14.x