Integrity of class locking
An issue with the integrity of the class locking process in Omnis Studio had been reported to us. We would like to assure everyone that we take matters of this nature very seriously, and as soon as we received information on this, our development team acted to consider approaches to mitigate this situation. We have thoroughly investigated the issue and have successfully implemented changes that will be available in Omnis Studio 11 Rev 35439, to alter the behaviour that made this operation possible.
We become aware of a technique being used on Omnis libraries in an ‘always private state’, to enable in specific circumstances library access and to unlock classes. In the process that was demonstrated to us, whilst the process of unlocking the class was completed, this method resulted in the library being left in a potentially corrupt state with unpredictable consequences then occurring during reading, writing or execution.
The upcoming Studio 11 Rev 35439 patch makes libraries in an ‘always private state’ more secure by implementing additional support offering further restrictions. These additional restrictions can now be set in this latest patch of Studio 11.
It is recognised that the integrity and security of Omnis Studio Libraries is an ongoing project, and future scheduled work will enhance both the class lock & ‘always private’ library system.
If you have any further questions or need any additional information, please don’t hesitate to reach out. Thank you for your continued support and understanding.
We have begun immediately investigating the report as circulated 31st July 2023. We will of course update on this as soon as our investigations are completed.
Sorry, there were no replies found.
Log in to reply.