eturnal 1.9.1

Added

• Allow for adding the special keywords default or recommended to the
  blacklist. The former expands to the addresses blocked by default, the
  latter includes the former and additionally expands to a number of networks
  recommended
  to be blocked.
• Fall back to reading the relay port range boundaries from environment
  variables when relay_min_port and/or relay_max_port aren't specified.
• Docker: Adjust image ENTRYPOINT to provide a way to autodetect (in most
  cases) the Docker host's IPv4 address during container startup within isolated
  network environments, without explicitly defining the IPv4 address (with an
  ENV variable or a configuration file).

Changed

• If an EPMD process is spawned during
  eturnal startup, let it listen on localhost only (#9). (Note that our Linux
  packages and container images are
  configured to not start
  an EPMD process.)
• Omit the code location from log messages, except when debug logging is
  enabled.
• Apply other minor logging improvements.
• Docker: Reduce image size. IMPORTANT: A custom eturnal.yml configuration
  file should be mounted to the default path /etc/eturnal.yml or to a custom
  path defined with ETURNAL_ETC_PREFIX, as mounting it to
  /opt/eturnal/etc/eturnal.yml will prevent the container to start up
  successfully.
• Binary release: Update Erlang/OTP from 25.0.2 to 25.0.3.
• Windows: Update to LibYAML 0.2.5.
• Windows: Update to OpenSSL 3.0.5.