I also followed this post
we are working on ssl and also SSL v2 will also be there soon we already pushed all updates in v2.3.4-dev and will be available in normal update as well
Sorry to say that the problem persists.
Do you have any other solutions to suggest?
Team lied and said it was fixed in the last release of 2.3.4, the issue is NOT fixed and it still happens
What I mean is to provide at least one way to block it. I have tried every which way but have not managed to block the regeneration of certificates. I am certainly not very capable, for goodness sake, but I would have expected an answer in that direction.