ROIS
Security
When ROIS runs on a central machine and can be accessed by different users, it may be necessary to protect your knowledge. ROIS supports different levels of protection. The security level can be configured via the projects file.
In case you just want to prevent changes to a ROIS models in a project you can just add the attribute access with the value read to the Project tag of the relevent project. All users that log into your ROIS Server on the project can only browse the models in that project and no one is allowed to make changes to the models.
<Project access="read">
<Name>ReadOnlyProject</Name>
....
<Project>
If you want to give some users write access to a ROIS model but want to allow other users only read access, you can add the tag Users to the relevant project in the projects file. In the example, trusted_user1 and trusted_user2 have write-access to the ROIS models in the project, while all other users only have read-access.
<Project>
<Name>SomeProject</Name>
<Users>
<User access="write" name="trusted_user1"/>
<User access="write" name="trusted_user2"/>
<User name="*" access="read"/>
</Users>
....
</Project>
ROIS also provides a more secure than just based on user names. Each user has a ROIS licence file which includes a unique private key. The corresponding public key may be included in the projects file to make sure that only the user with that private key can access the models in a project. The private and public key pair are based on the RSA public key system with a length of 256 bits.
<Project>
<Name>SomeProject</Name>
<Users>
<User access="write" name="trusted_user1"/>
<User access="write" name="trusted_user2">5253413100010001A5EA4D4E25BA9237271C73BF610B9F2782154559E40BC628284AEDB1D25F2BEED1069A32E05515E28DA09BB148F7AFEAD1210348397232B9A345E0247ADBD6E0</User>
<User name="*" access="read"/>
</Users>
....
</Project>
If you also want to encrypt the communication between client applications and the ROIS Server, you should add the attribute secure to the relevant project in the projects file. If you don't specify a user key, the communication is encrypted with a blowfish key. The weak point in this scenario is that the blowfish key is send over the network.
<Project secure="yes">
<Name>SecureProject</Name>
....
<Project>
It is also possible to use the RSA key pair of a user to encrypt the blowfish key used for the communication. Just specify the attribute secure as above and add the tag Users with the relevant user and his public key. The blowfish key is then encrypted with the public key of the logged in user, and can only be descrypted by a client application with access to the private key of the user.