Skip to content

Releases: XternA/spide-network

Spide Network v1.2.2

Choose a tag to compare

@XternA XternA released this 08 May 00:03
1.2.2
6cf3922
  • Minor update just to ensure future changes to the image don't interfere with /etc/machine-id that is being set or parsed.

Full Changelog: 1.2.1...1.2.2

Spide Network v1.2.1

Choose a tag to compare

@XternA XternA released this 06 May 17:19
1.2.1
  • Ability to reuse the same Machine ID to deploy the container for the same device that has been already registered.

This only works for new devices that haven't been registered in the dashboard yet as previously already registered devices, we don't know what the Machine ID was, because the Machine ID used is rehashed to produce the Device Key.

With the machine ID, we will be able to always reproduce the same Device Key we match for the device we want to set, but the reverse can't be achieved due to closed source.

Full Changelog: 1.2...1.2.1

Spide Network v1.2

Choose a tag to compare

@XternA XternA released this 06 May 14:20
1.2
be6f6c1

This release fixes the issue with the fixed device key being the same when deployed as a docker container.

The fix addresses when deploying a new container to guarantee a new device key ID, on restarting the container this key will persist. If the container is terminated and redeployed again, a new key is given.

The only problem is that new device registration will need to be added to the account dashboard each time which will clutter the registered device. However, until there is a solution to use the existing device key and reverse the operation, there will currently be no support for device key re-use.