v1.0.1

Security

Upgrade if you run with EnableProxyProtocol behind a proxy.

• The PROXY command comes first in a session, and a later one gets a 503
  reply. A proxy writes its header before it passes on anything of the
  client, so a PROXY command that comes after a command comes from the
  client behind the proxy.

  handlePROXY took every one of them. Each wrote Peer.Addr and ran the
  ConnectionChecker again, so a client behind the proxy could take the
  address of another one. Every checker of the session reads Peer.Addr.

  This changes behavior. A client that sends PROXY twice gets a 503
  for the second one, where it got a greeting before.

The v2 line carries the same fix in v2.4.0.

Fixed

• The CI workflow runs for the v1 branch. The triggers named master, so no
  workflow ran for a push to the branch or for a pull request against it.