The future... C++Builder... MJFSecurity...
If you're looking at this page then you are more than likely a user of Borland C++Builder and my security suite known as MJFSecurity.
I've been a bit slack on the continued development of MJFSecurity due to the unknown future of C++Builder (BCB). Many customers have already moved away from BCB and there has been a definite impact on my own sales (although it is not dead yet). Lately there has been rumours of a possible future but we'll just have to wait and see.
As for MJFSecurity, whether you are a current user of MJFSecurity or someone who is reviewing it for their needs in application development, I'm interested in hearing back from people like you. Tell me what you think of MJFSecurity, the features it has and what you think it is missing.
I personally have ideas for upcoming versions of MJFSecurity based on options I have required in bespoke projects I have worked on. Often, due to time restraints, I have made custom modifications for customers and now I think it is time to build some of these ideas into the base product.
Such features include:
* Ability to deactivate some/all of the tamper detection methods once an application has been registered. The types of tamper detection that can be disabled will be dependant on the type of licensing you use. Subscription licensing, for example, should not deactivate the detection of winding the clock back. Although careful thinking will be required when using this facility it has become obvious on some projects there is a definite need for this feature.
* The ability to detect and download patches. MJFSecurity currently has the tools required to apply patches dynamically (even while the application is running) but there is no automatic feature to download the required patches.
* A better custom splash screen implementation. I'd like to develop a custom interface that the built-in splash screen and your own custom screens could use. By using a common interface MJFSecurity would be more consistant in the implementation.
There's heaps more but blog's should be short and this one is already too long.
If you have any opinions or comments you want to share I'd like to hear back from you.
