Skip to content

Version 1.6.0
Compare
Choose a tag to compare
@llemeurfr llemeurfr released this 04 Feb 09:32
· 122 commits to master since this release
V1.6.0
bff371c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

  • Restores the capability for the lcpencrypt utility to fetch the input file from a remote http server.

  • Offers an alternative way to store encrypted publications: the lcpencrypt utility can now store an encrypted publication to its final storage location (file system or S3 bucket), and does not rely on the License Server to do so. In such a case, the lcpencrypt utility notifies the lcpserver of the encryption of a new publication with its storage URL as a parameter.

An implementer can therefore control storage folders or S3 buckets as he needs, e.g. use one folder/bucket per month, one folder/bucket per type of publication, even one folder/bucket per publication if this is his choice.

The evolution is totally backward compatible, i.e. implementers are able to keep their current architecture and configuration file. They are also able to move to the new architecture without the requirement to change the structure or content of their active database. Implementers willing to move to the new architecture will just have to modify their config file, restart their lcpserver and use lcpencrypt with new parameters.

Assets 2
Loading