| restricting access to XMI from EMFStore client. [message #1734907] |
Mon, 13 June 2016 11:40  |
Eclipse User |
|
|
|
I have some data stored as a large XMI file which I would like to allow other users to view and edit using an EMFStore client (ECP with EMFstore provider) . However I dont want the users to have access to the actual XMI file or to be able to recreate it easily. I can easily create a custom version of ECP for users to use which doesn't have an 'export' menu item. I was wondering though if the XMI files are stored in the client side anywhere such as in .emfstore\client or maybe the models are in memory only.
Thanks,
Neil
|
|
|
|
|
| Re: restricting access to XMI from EMFStore client. [message #1735176 is a reply to message #1735076] |
Thu, 16 June 2016 02:08  |
| Eclipse User |
|
|
|
Hi Neil,
I am not a fan of "half secure" solutions, but encrypting the files
would at least make it a little harder to get the data.
However, I wonder, how you want to encrypt something locally, without
storing the secret key somewhere locally, so it is more an obfuscation
anyways.
Best regards
Jonas
On 15.06.2016 13:09, Neil Mackenzie wrote:
> Thanks Jonas.
> Maybe I could create a custom client. This client would encrypt the text
> files it stores in .emfstore, and then decrypt them when it loads them
> again. Do you think this would work? Maybe it is not so simple if there
> is code that uses classes which requires the actual files.
> If someone goes to the effort of writing a new plugin then they can have
> the XMI files :)...I guess there are ways to prevent this also (like a
> custom client and server which add some small step to the connection
> process, so that only the custom client can connect to the server). Note
> that in my case the server would be on a different machine that the
> client users dont have access to.
|
|
|
Powered by
FUDForum. Page generated in 0.10082 seconds
Home
...I guess there are ways to prevent this also (like a custom client and server which add some small step to the connection process, so that only the custom client can connect to the server). Note that in my case the server would be on a different machine that the client users dont have access to.