Hello folks!
I would like to install CipherMail for testing and stumbled across a “little” problem.
We updated our systems from Debain 11 (Bullseye) to Debian 12 (Bookworm).
As of now the CipherMail Packeges supplied for download need the openjdk 11. But this is no more available for installation from the normal repo. The latest Version is openjdk 17.
I know that I could use a other repo to get the openjdk 11 but as the version 11 will run out in October of 2024 I would not start here.
Is there a new release planned which includes the support of openjdk 17, or is there a way to install CipherMail around the prerequisites which are in the package?
Thank you in advance
Unfortunately the current release requires Java 11. We are however working hard on a major update (we are already working on for a long time) The upcoming major release requires >= Java 17.
Unfortunately we do not yet have a release date.
Hi Martijn,
I don’t know if you can tell us, but what major features and changes are planned for the next release? Just curious.
Hej Martjin!
Thanks for the information.
Most likley I will now test with the old Java version and will wait for the new release, befor we can take it any further or to produtcion.
Thanks Sascha
Hey there!
Is there any new information about the new major release which would be able to run on Debian 12?
Thanks in advance.
Sascha
Hello,
it has somehow become rather quiet. Somehow there are absolutely no more updates and this at a time when new security vulnerabilities are discovered almost daily.
Is there somehow an ETA or something similar here?
The whole thing is currently very risky to use. It is currently ruled out for commercial use because the dependencies are too old and too risky.
If there is not enough time for a major update - could you at least concentrate on security updates?
Thank You.
For about the last 2 years we are working hard on a major update. Because a lot of libraries we were using had major updates we had to rewrite most parts. Unfortunately it took somewhat longer than we had anticipated. To good thing is that since large parts were rewritten, we could fix a number of things we wanted to do differently. For example, the back-end is now completely configurable with a REST api. The REST api has an extensive authorization module where every action and setting requires a specific permission. The UI has been rebuilt completely. It now uses React. There is now also a fully functional cli (which connects to the back-end using the REST api) which allows you to fully script the gateway. There are lots of other changes and improvements which will be explained in a blog when we release it.
The release is almost ready. It has been in production for some time now. We will need to work on the documentation however.
I’m not sure how tech savvy you are but you might try the new version even though it’s not yet “officially” released. You can build everything yourself. If you however prefer a deb/rpm (or VM), let me know and I will create a release candidate build for you.
All code can be found in our community gitlab repo:
About supporting the old release, we are still working on updates and we will keep track and fix security issues