las2peer Release 0.7.0
Finally we are happy to release las2peer 0.7.0 introducing exciting new features paving the path to secure, self-deploying services.
- A new service API, making features more accessible and intuitive to use for new developers.
- More secure services: Services are now isolated from the core.
- Easier service deployment: Services can be uploaded to the network once and deployed on any node with a single command!
- A node admin connector, bringing together all new features in a nice GUI allowing
- easy management of the node,
- uploading services and providing and
- an easy-to-use widget space for service front ends.
- A single las2peer-bundle jar containing everything to get started with las2peer: Simply make your service depending on “las2peer-bundle”!
- Simpler set up of service dependencies: The new build script in the Template project bundles all service dependencies in one single jar, making managing dependencies a lot easier for service developers.
As always, we provide a guide for service developers to migrate their services.
The complete change log is available on GitHub, changes included are:
- [LAS-326] – Agent Id is not cryptographicaly safe
- [LAS-401] – Replace SHA1 With SHA256 For Signatures And SHA512 For Secure Hashes
- [LAS-402] – L2pNodeLauncher interface unsafe
- [LAS-419] – Serve favicon requests via WebConnector
- [LAS-420] – Global RMI Calls With Anonymous Agent Not Possible
- [LAS-422] – JUnit Tests not working by default
- [LAS-193] – Javadoc lacks many @params and @throws descriptions
- [LAS-257] – Use Interfaces for service API
- [LAS-334] – node-id-seed is a common error source
- [LAS-367] – Add debug mode option to L2pNodeLauncher
- [LAS-376] – Simplify dependency management
- [LAS-377] – get rid of anonymous agent (at least of the key pair)
- [LAS-392] – Nodes should auto-reconnect to the same network after restart
- [LAS-404] – Auto Create Local Properties File For Productive Deployments
- [LAS-417] – Check JUnit tests for common issues