0.3.0 - Authentication & New Versioning Scheme

Authentication

Firsts things first, Authentication! I've added a simple secret key that is required to access the AlwaysAuth auth server instance, this will stop people from creating fake authentication requests.

On top of this the database will now have the ip address encrypted with the same secret key, this will ensure any database leaks do not leak people's ip's (unless someone got a hold of your secret key as well).

New Config Options

The config is setup to auto update, so you shouldn't have to regenerate it or anything. But just so you know there are two new values:

authentication-enabled=true
secret-key=GENERATED ON STARTUP

Standalone Servers

If you are using a standalone instance for multiple servers, simply all the servers need to match the standalone instance's secret key, and then they will be able to connect to the standalone server.

Disabling Authentication

If you so choose you can disable authentication which can leave you open to possible false authentication attacks on your server, this is highly not recommended but left as an option if you so choose too for whatever reason.

Note this will not disable the database IP encryption.

New Version Scheme

I will be implementing (properly) the SemVer format which follows the Major.Minor.Patch format, so right now we are on Major version 0, Minor version 3, and Patch version 0.