Sentinel | License Management Solution v2.3.0

• Several major Sentinel internal dependencies have been updated, improving the general performance and security of the application.

• Implemented optional symmetric encryption on Sentinel responses, making it significantly harder for attackers to decipher the meaning of API responses.
• Added timestamps to all API responses. Combined with encryption, Sentinel effectively deters network replay attacks.

If you are upgrading, change config.yml's config-version to 2 and add the following section:

YAML:

# Symmetric (AES) encryption settings for server responses.
encryption:
  # If server responses should be encrypted.
  # This is recommended, as it prevents users from tampering with the response.
  # Of course, you will need to decrypt the response on the client side.
  # Our official wrappers have support for this.
  enabled: false
  # The secret key used for symmetric encryption.
  # Leave empty for automatic generation on initial startup.
  secret: ""

sentinel-java-wrapper v1.1.0
• Added support for encrypted responses (automatic decryption, given a secret key).
• Added timestamp to the Response object.

• Added a /mylicenses command which allows the Discord user to view all license keys attached to their account through an ephemeral message.
• Added a "%licenses%" placeholder to the activity text in bot.yml, which can display the number of licenses that currently exist. Updates live when a license is created/deleted.

• Fixed an issue with embed message timestamps showing the bot start time instead of the current time (if the timestamp value is set to -1, the default value, in the bot.yml).
• Fixed corrupted downloads. Sentinel is now distributed as a RAR file to work around the BuiltByBit bug. A proper fix is still in the works by Justis.

sentinel-java-wrapper v1.0.5
• Added the utility method SentinelClient.getCurrentHwid() to get the HWID of the current machine.

• Several major dependencies of Sentinel have received major updates. This update is highly recommended to ensure the performance and stability of the product.

• Fixed an issue with durations for license expirations not being parsed correctly.
• Fixed a typo that prevented the default auth-only user from working as expected. If you are upgrading from an older version, for each user in config.yml, change the "permission:" key to "permissions:".

• Sentinel now requires a license key to start, due to BuiltByBit's placeholder injector corrupting Sentinel's JAR file. This issue has been reported and is currently being fixed.

Upgrading from 1.1.0
If you are upgrading from Sentinel 1.1.0, make sure to add license-key: "YOUR_KEY_HERE" to your config.yml. Create a ticket at https://demeng.dev/discord to obtain your license key.

• Auto-generated license keys will now be segmented and separated by dashes to improve user experience.
• Added product roles- give users a custom role on Discord when their license is created.
• Added license authentication logs on Discord.