This is a small bugfix release.

If you had an active and valid session from a v0.15.0, did an update to v0.16.0 and your session was still valid,
it did not have existing information about the peer IP. This is mandatory for a new feature introduced with v0.16.0
though and the warning logging in that case had an unwrap for the remote IP (which can never be null from v0.16.0 on),
which then would panic.

This is a tiny bugfix release that just gets rid of the possible panic and prints UNKNOWN into the logs instead.

Changes

• print UNKNOWN into the logs for non-readable / -existing peer IPs
  6dfd0f4

Images

Postgres

ghcr.io/sebadob/rauthy@sha256:e6b4c990c6317b9f65d7b81a4dee7cccf0e82c602a11f012c4c6086ed0ccd0be

sdobedev/rauthy@sha256:e6b4c990c6317b9f65d7b81a4dee7cccf0e82c602a11f012c4c6086ed0ccd0be

SQLite

ghcr.io/sebadob/rauthy@sha256:91d126209dfb15b092b91a72a65cb3e56c6d048f7b77b21c6e8ed3a0e68a5de1

sdobedev/rauthy@sha256:91d126209dfb15b092b91a72a65cb3e56c6d048f7b77b21c6e8ed3a0e68a5de1