You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
The last official release of SoftHSM is 3 years old and with a lot of pull requests are waiting to be reviewed or merged.
The continuous integration seems broken also ?
Is there any willingness or plan to "revive" this very useful library ?
Well, given the recent activity by @halderen, I think the response to my question is "Yes".
While I'm at it, any plan for a new release with all the changes ? Or are there any more PRs that are targeted for merging ?
@antoinelochet from all the dead links on the SoftHSM web site, I would guess the project is no longer being supported? Did you ever receive a response to your three month old query?
As for CI there is a PR for a CI via Github Actions in #733, this can probably be extended in many ways,
but I hoped it could help to get other open PRs merged.
While I'm at it, any plan for a new release with all the changes ?
You are right, it seems that 25 merged PRs are not included in a tag/release.
It would be good to get an understanding what we can help out with to enable a new release.
First of all, let me apologise for the long radio silence in the SoftHSM v2 project.
In this message, we would like to set out the current state of SoftHSM v2 development. Let me start with a bit of history to provide context. SoftHSM v2 was first developed as a successor to SoftHSM, which was originally a component of the OpenDNSSEC project. The rationale for starting SoftHSM v2 was simple: the original SoftHSM had no security features and stored key materials in clear text in a database. SoftHSM was only ever intended as a placeholder PKCS #11 implementation for use with OpenDNSSEC under the assumption that most user of OpenDNSSEC would eventually use a "real" HSM with its own PKCS #11 module and that SoftHSM would only be used for testing and development. When it became clear that many deployments used SoftHSM in production, a decision was made to develop a much more secure successor which we called SoftHSM v2.
Development of SoftHSM v2 was initially done by a development team consisting of staff members of IIS (the registry for .se) and SURFnet (the National Research and Education Network in The Netherlands), both also contributors to OpenDNSSEC. Over time, the team members changed job positions a number of times, and eventually all team members ended up in roles that were incompatible with sustained development work on SoftHSM v2. While team members did occasionally spend time on the code base in their spare time, they do not have sufficient spare cycles to perform maintenance let alone develop new features.
As maintainers of the OpenDNSSEC project, NLnet Labs also worked on SoftHSM v2, verifying and merging pull requests from the community and fixing some of the bugs reported in the issue tracker. At this time, this is also best effort, and no significant development time is available to spend on the project.
Given the above, the current state is that development on SoftHSM v2 is dormant and not likely to pick up significantly in the near future. We are conferring as a team on how to proceed in the future, but this will likely take us until at least the summer of 2024.
I wish I could provide a more definitive outlook for the future.
On behalf of the SoftHSM v2 developers,
Roland van Rijswijk-Deij
Reacted by Marco Davids, niek-sidn, subbink, LiaoChinTe and Lars Silvén
Thanks for elaborating, it certainly helps with understanding the current state of this project. Your situation is of course understandable, as priorities and responsibilities shift over time.
I just wanted to put out there that SoftHSM v2 is still an remarkably useful piece of software for anyone working within the niche field of HSMs and PKCS#11 and hope you can work out a plan. At any rate, there is still a decent amount of interest from potential contributors 🙂
Activity
antoinelochet commentedon Jul 25, 2023
@rijswijk Sorry to @ you like this but as the last merger of this project, can you share some news maybe ?
antoinelochet commentedon Aug 22, 2023
Well, given the recent activity by @halderen, I think the response to my question is "Yes".
While I'm at it, any plan for a new release with all the changes ? Or are there any more PRs that are targeted for merging ?
antoinelochet commentedon Nov 2, 2023
It seems that I have talked too soon.
Any update on a future release ?
ptdecker commentedon Feb 14, 2024
@antoinelochet from all the dead links on the SoftHSM web site, I would guess the project is no longer being supported? Did you ever receive a response to your three month old query?
antoinelochet commentedon Feb 14, 2024
I really wish I had.
Some merges happened not so long ago so I think some of the mainteners still drop here from time to time.
bjosv commentedon Mar 7, 2024
As for CI there is a PR for a CI via Github Actions in #733, this can probably be extended in many ways,
but I hoped it could help to get other open PRs merged.
You are right, it seems that 25 merged PRs are not included in a tag/release.
It would be good to get an understanding what we can help out with to enable a new release.
antoinelochet commentedon Apr 5, 2024
Any news on my query ?
rijswijk commentedon Apr 9, 2024
Dear members of the community,
First of all, let me apologise for the long radio silence in the SoftHSM v2 project.
In this message, we would like to set out the current state of SoftHSM v2 development. Let me start with a bit of history to provide context. SoftHSM v2 was first developed as a successor to SoftHSM, which was originally a component of the OpenDNSSEC project. The rationale for starting SoftHSM v2 was simple: the original SoftHSM had no security features and stored key materials in clear text in a database. SoftHSM was only ever intended as a placeholder PKCS #11 implementation for use with OpenDNSSEC under the assumption that most user of OpenDNSSEC would eventually use a "real" HSM with its own PKCS #11 module and that SoftHSM would only be used for testing and development. When it became clear that many deployments used SoftHSM in production, a decision was made to develop a much more secure successor which we called SoftHSM v2.
Development of SoftHSM v2 was initially done by a development team consisting of staff members of IIS (the registry for .se) and SURFnet (the National Research and Education Network in The Netherlands), both also contributors to OpenDNSSEC. Over time, the team members changed job positions a number of times, and eventually all team members ended up in roles that were incompatible with sustained development work on SoftHSM v2. While team members did occasionally spend time on the code base in their spare time, they do not have sufficient spare cycles to perform maintenance let alone develop new features.
As maintainers of the OpenDNSSEC project, NLnet Labs also worked on SoftHSM v2, verifying and merging pull requests from the community and fixing some of the bugs reported in the issue tracker. At this time, this is also best effort, and no significant development time is available to spend on the project.
Given the above, the current state is that development on SoftHSM v2 is dormant and not likely to pick up significantly in the near future. We are conferring as a team on how to proceed in the future, but this will likely take us until at least the summer of 2024.
I wish I could provide a more definitive outlook for the future.
On behalf of the SoftHSM v2 developers,
Roland van Rijswijk-Deij
ijsf commentedon May 3, 2024
Thanks for elaborating, it certainly helps with understanding the current state of this project. Your situation is of course understandable, as priorities and responsibilities shift over time.
I just wanted to put out there that SoftHSM v2 is still an remarkably useful piece of software for anyone working within the niche field of HSMs and PKCS#11 and hope you can work out a plan. At any rate, there is still a decent amount of interest from potential contributors 🙂
antoinelochet commentedon Oct 30, 2024
Hello @rijswijk,
We are way past summer 2024, have you decided what you want to do ?